Is there anybody having successfully connecting VS2015 to SQLServer 2008 (original, not R2) Express? the SQLServer seems to be running fine (connection using Management studio is okay) but I could not get connected to it using VS15. The error says something about the Microsoft.SqlServer.Management.Sdk.Sfc, Version=12.0.0.0 assembly
This post provides a nice solution to some cases but it does not seem to work in mine. If I understand correctly, the VS15 assumes the use of SharedManagementObject assembly 12.0.0.0 for Sqlserver 2014. But I'm running 2008 version and this package certainly cannot be installed.
Anybody knows a workaround for it?
== UPDATED according to my answer ==
So what if I deploy my application, which uses Entity Framework (for which I need to connect VS to SQLServer), on a machine that does not run VS2015, nor some items from the feature pack?
Thank you!
Well I was stupid. And it turns out, indeed, to be the problem of visual studio 2015 always assuming the assembly for SQLServer2014. I ended up installing 2 items from the SQL server 2014 feature pack including:
System CLR Types, which is the prerequisites for
Management Objects
And restart the Visual Studio (it would not work without this damn critical step).
Related
I have been searching for a while on this and have no real direction on what the problem may even be. I haven't done SSIS for about 5 years and even 5 years ago I only did one or two.
I have Visual Studio 2012 on my machine. I installed SSDT so that I could write an SSIS package. I have the package written and working locally but when I try to set up a job in the SQL Agent on the server I get this error after selecting the package:
I have looked into this error and none of the resolutions I have found are working. My project is already set to not use 64 bit mode. I'm kind of thinking this might have to do with the fact that the version of SQL Server on that machine is just 2008 and that maybe that means it has an incompatible SSIS runtime. I don't know if there is an additional runtime I need to install to get this to work and I don't know if it's backward compatible with the old runtime they are using if that's even the problem.
I can't find any information online about setting up the environment for an SSDT SSIS package..
Please help.
Thanks
You have a package built against the SQL Server 2012 Integration Services object model. You are attempting to execute it on a 2008 instance. Backwards compatibility is not an option.
You need to either update the 2008 instance to 2012 (there is a licensing change to be aware of) or recreate your package using the 2008 model.
There are 2 steps you have to do:
1) Build you package using correct version - Update 2208 Instance to 2012
2) If you have multiple versions install and you try to deploy using .ispac file, it will most likely pick the latest version. To resolve the issue, you have to pick the correct version of Installer by going to where it is installed. In my case it is (C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn)
I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation.
I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server.
I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.
So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue
So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:
Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.
The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.
I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.
Any help would be appreciated
Thanks,
Doug
This might help: How to edit SSRS 2008R2 Reports in Visual Studio 2012?
I've been reading about mySQL DataSource and the ability to use mySQL with Entity Framework, but I can't really generate EF with mySQL without the use of the DataSource Dialog
How can I add mySQL Database to such dialog?
This is what I have done so far:
Installed mySQL Connector v.6.5.4
Restarted n-times my Windows 7 machine
Read all about how well mySQL Connector works on previous versions of Visual Studio
I have just read from mySQL Forums that mySQL will ship Visual Studio 2012 integration with mySQL Connector v.6.5.5
We'll be adding support for VS 2012 in Connector/NET 6.5.5 and later 6.6.x version
http://forums.mysql.com/read.php?38,546265,564533#msg-564533
and give a link to test a trick
http://social.technet.microsoft.com/wiki/pt-br/contents/articles/10476.instalando-mysql-connector-no-visual-studio-2011-beta.aspx
and here is the vsix file if you follow the tutorial (In Portuguese)
Microsoft Visual Studio Extension for mySQL: http://cl.ly/JqXO
just download and double click...
then, you will get all to work
Using Visual Studio 2012 Professional
One clarification: Visual Studio Express DOES NOT support MySQL .NET Connector as extension.
You still may use it adding reference to MySql.Data.dll file that you may find in MySQL Connector installation folder (for me it was W:\Program Files\MySQL\Connector NET 6.5.4\Assemblies\v4.0).
After that you may use it like this:
using MySql.Data.MySqlClient;
...
var mycon = new MySqlConnection();
According to this page: http://dev.mysql.com/downloads/connector/net/
"Starting with version 6.7, Connector/Net will no longer include the MySQL for Visual Studio integration. That functionality is now available in a separate product called MySQL for Visual Studio available using the MySQL Installer for Windows (see http://dev.mysql.com/tech-resources/articles/mysql-installer-for-windows.html)."
Visual Studio 2012 is not yet supported by MySQL Connector v.6.5.4. You can't add a connection to MySQL in the Server Explorer to begin with.
According on this post, support will be added on MySQL Connector v.6.5.5
Connector/NET 6.5.5 does not support VS2012, but Connector/NEt 6.6.x does.
However Visual Studio Express editions are not supported, hence the only way to work in Entity Framework and Visual Studio Express and MySql (or other database different than SQL Server for that matter) is using code first.
It wouldn't matter if you had the MySQL driver showing as far as I can tell. I'm running VS 2012.3 and if I try to create a Data Connection in VS Server Browser, I can get as far as selecting the MySQL driver and no more. If I try typing a servername/username/password (any of the fields), the window just disappears and YES, it's only when the MySQL driver is being used so NO it's not vs (not exclusively) causing the problem. Go ahead and say that it's my environment but you'd not be able to justify that even remotely compared to the FACT of what is happening. ALL my other software/extentions/add-in/libraries work just fine. No surprise either seeing how buggy the "3 minute" Windows Installer was. Had to uninstall/reinstall a server instance to get to the configuration wizard and there is no other apparent way to configure an instance without it. I'd rather have the old setup. /rant
Downloaded and install Download MySQL for Visual Studio http://dev.mysql.com/downloads/windows/visualstudio/1.1.html
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Below is a list of the SQL components that I installed in the Visual Studio 2010 Professional setup. Sadly, while trying to work I could not find SQL Server Management Studio 2008.
Is there a way to download SQL Server Management Studio 2008 separately and install only that component?
Since in the past I installed SQL Server Management Studio 2005 with a whole new instance of SQL Server 2005 and had couple of instances, and it was a bit messy.
I found some articles to be of major use:
This link is an experience someone else had:
http://goneale.com/2009/05/24/cant-install-microsoft-sql-server-2008-management-studio-express/
This link has the exact steps involved to install everything properly:
http://www.codefrenzy.net/2011/06/03/how-to-install-sql-server-2008-management-studio/
This link confirms the previous link:
https://superuser.com/questions/88244/installing-sql-server-management-studio-when-vs2010-beta-2-is-already-installed
My Instructions
I am not sure if my instructions will be 100% accurate, but in my instance, because I installed VS2010 on a fresh copy of Windows 7, the VS2010 installer installs SQL Server 2008 Express for you, so from this point I just need the Management Studio.
What I gathered from these explanations is to do the following:
Download the SQL Server Management Studio install from
http://www.microsoft.com/download/en/details.aspx?id=22973
Run the setup, when you get to the point where it asks you to "Perform a new installation of SQL Server 2008" or "Add features to an existing instance of SQL Server 2008", this part is the CONFUSING PART (HEY MICROSOFT TAKE NOTES, DON'T DO THIS KIND OF STUFF).
As much as you want to select "Add features to an existing instance of SQL Server 2008" DON'T!!!!
You need to select "Perform a new installation of SQL Server 2008". It doesn't sound right I know - it is very confusing and counter intuitive, but this seems to be the way to install management studio. :(
Press next until you see the features selection portion. Heeeeeyyyy look at that, it has a check box for Management Studio. It should be selected already, if not then select it of course and press next.
Press Next next next next next next... basically just install it at this point.
Enjoy, it has installed.
If you have the SQL Server 2008 Installation media, you can install just the Client/Workstation Components. You don't have to install the database engine to install the workstation tools, but if you plan to do Integration Services development, you do need to install the Integration Services Engine on the workstation for BIDS to be able to be used for development. Keep in mind that Visual Studio 2010 does not have BI development support currently, so you have to install BIDS from the SQL Installation media and use the Visual Studio 2008 BI Development Studio that installs under the SQL Server 2008 folder in Program Files if you need to do any SSIS, SSRS, or SSAS development from the workstation.
As mentioned in the comments you can download Management Studio Express free from Microsoft, but if you already have the installation media for SQL Server Standard/Enterprise/Developer edition, you'd be better off using what you have.
Download SSMS 2008 Express
I am just updating this with Microsoft SQL Server Management Studio 2008 R2 version. if you run the installer normally, you can just add Management Tools – Basic, and by clicking Basic it should select Management Tools – Complete.
That is what worked for me.
The accepted answer was correct up until July 2011. To get the latest version, including the Service Pack you should find the latest version as described here:
http://support.microsoft.com/kb/2527041
For example, if you check the SP2 CTP and SP1, you'll find the latest version of SQL Server Management Studio under SP1:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
Download the 32-bit (x86) or 64-bit (x64) version of the SQLManagementStudio*.exe files as appropriate and install it. You can find out whether your system is 32-bit or 64-bit by right clicking Computer, selecting Properties and looking at the System Type.
Although you could apply the service pack to the base version that results from following the accepted answer, it's easier to just download the latest version of SQL Server Management Studio and simply install it in one step.
For any of you still having problems as of Sept. 2012, go here: http://support.microsoft.com/kb/2527041 ...and grab the SQLManagementStudio_x(32|64)_ENU.exe (if you've already installed SQL Server 2008 Express R2), or SQL Server 2008 Express R2 with Tools, i.e. SQLEXPRWT_x64_ENU.exe or SQLEXPRWT_x32_ENU.exe (if you haven't).
From there, follow similar instructions as above (i.e. use the "Perform new installation and add shared features" selection, as "Management Tools - Basic" is considered a "shared feature"), if you've already installed SQL Server Express 2008 R2 (as I had). And if you haven't done that yet, then of course you're going to follow this way as you need to install the new instance anyway.
This solved things for me, and hopefully it will for you, too!
SQL Server Management Studio 2008 R2 Express commandline:
The answer by dyslexicanaboko hits the crucial point, but this one is even simpler and suited for command line (unattended scenarios):
(tried out with SQL Server 2008 R2 Express, one instance installed and having downloaded SQLManagementStudio_x64_ENU.exe)
As pointed out in this thread often enough, it is better to use the original SQL server setup (e.g. SQL Express with Tools), if possible, but there are some scenarios, where you want to add SSMS at a SQL derivative without that tools, afterwards:
I´ve already put it in a batch syntax here:
#echo off
"%~dp0SQLManagementStudio_x64_ENU.exe" /Q /ACTION="Install" /FEATURES="SSMS" /IACCEPTSQLSERVERLICENSETERMS
Remarks:
For 2008 without R2 it should be enough to omit the /IACCEPTSQLSERVERLICENSETERMS flag, i guess.
The /INDICATEPROGRESS parameter is useless here, the whole command takes a number of minutes and is 100% silent without any acknowledgement. Just look at the start menu, if the command is ready, if it has succeeded.
This should work for the "ADV_SSMS" Feature (instead of "SSMS") too, which is the management studio extended variant (profiling, reporting, tuning, etc.)
I have an application that uses SQLXML to access data on the database. We have it working on a Windows 2003 server and SQL Server 2005. Now the client wants to install it on Windows 2008 and SQL Server 2008 and we are getting errors like:
Microsoft.Data.SqlXml.SqlXmlException: Class not registered ---> System.Runtime.InteropServices.COMException (0x80040154): Class not registered at Microsoft.Data.SqlXml.Common.UnsafeNativeMethods.
ISQLXMLCommandManagedInterface.ExecuteToOutputStream() at Microsoft.Data.SqlXml.SqlXmlCommand.innerExecute(Stream strm)
... etc etc
This is driving me crazy. SQLXML is quite an obsolete technology, and we are trying to use it with the latest SO. I can't find official information about SQLXML and Windows 2008, it seems it's not officially supported but they don't say it's not supported either.
The SQLXML4.0SP1 installation seems to work fine, but it seems like it fails on runtime.
Do you have any ideas? Has someone tried anything like this?
The packages for SQLXML 4.0 SP1 were only available for download in the April 2009 release of the Microsoft SQL Server 2008 Feature Pack. Not sure why they don't appear in the 2008 R2 Feature Pack but they don't.
Here's your link to the Feature Pack
Direct links to the appropriate versions of SQLXML 4.0 SP1 can be found on that page
My recommendation would be to take advantage of the fact that it works on SQL 2005 to convert the code to not use SQLXML. You can take advantage of the fact it works to create tests that prove it works. Then do the conversion, and test again. If the tests still show it works, you've rid yourself of obsolete technology while there's still someone living who knows what the obsolete technology was meant to do.
Otherwise, after finding the fix for this immediate problem (maybe reinstall MSXML) you'll be having this discussion 20 years from now, but with the difference that nobody living knows what SQLXML used to be.
SQLXML is not installed to SQLServer by default. You should run SQL Server Installer, and add SQLXML feature.
I mean SQL Server 2008.
You are probably using ISAPI functionality, which is not supported in SQLXML 4.x
Install SQLXML 3.0 on Win 2008 Server (Vista,7) and for IIS 7.x change IIS 6 Management Compatibilty - allow IIS 6 Metabase Compatibility and IIS 6 Management Console (in Administrative Tools/Server Manager/"Roles - Webserver (IIS)"/ "Role Services" ).
On 64bit Win Server 2008 'Enable 32-bit Applications' for IIS/Application Pools.