I'm afraid I know the answer to this already, but I'm hoping someone can point me in a better direction. I just finished developing a large ETL project using VS2013. My dev machine has SQL Server 2012 installed, and everything works perfectly executing from within VS. However, I just went to deploy the project to another device running SQL Server 2012, and got a version error.
I thought if I could open the solution in VS2012, the packages might recompile correctly. However, I can't open them in VS2012 due to version errors again ("version can't be lower than current version" error). I'm pissed because everything worked fine in development with the VS2013/SQL2012 combo, but now suddenly it's no good?!?
Can someone please help me figure out how to get these packages downgraded to work with VS2012/SQL2012? There are only a few script tasks involved if that makes a difference. Mostly it's just basic SSIS tasks and data flows.
Thanks.
I found a workaround how you can "downgrade" your SSIS 2014 packages to SSIS 2012. I wrote it on my blog here:
http://vaniecastro.com/2015/02/26/how-to-downgrade-sql-server-integration-services-2014-packages-to-2012/
The idea is that you need to manually modify the XML file, change the PackageFormatVersion and replace ExecutableType property and componentClassID attribute values to use the DTSX2 Version 2012/01 values instead of the DTSX2 Version 2014/01 ones.
You can try using Visual Studio 2015 SSDT Preview. This now allows you to choose which version of SQL Server you want to target, including SQL Server 2012. I successfully downgraded my packages from VS 2013 / SQL Server 2014 to SQL Server 2012 this way.
https://msdn.microsoft.com/en-us/mt429383.aspx
Once the shell is installed, go to the Project menu=>Project Properties=>Configuration Properties=>TargetServerVersion and choose 2012.
Related
I have a client who has TFS 2010 and I need to setup my own installation on an Azure VM in order to do some testing, and help them migrate off of TFS 2010 to TFS 2015. However, I cant for the life of me seem to locate a setup .exe online for Team Foundation Server 2010. Is this still possible? Do I need a physical DVD?
The instructions here
https://www.microsoft.com/en-us/download/confirmation.aspx?id=24337
ask to use the physical DVD, but I dont have one.
According to this link https://social.msdn.microsoft.com/Forums/vstudio/en-US/56343ed9-6c0c-4c17-89d1-62b4bb3cf645/visual-studio-team-foundation-server-2010-setup-downloadable-link?forum=tfsbuild
Its available for MSDN subscribers, but I dont see any TFS versions below 2015 on MSDN download page.
I have found the service pack 1 install, but not the setup for the full product. can anyone help me locate a setup exe online so that I can get this running? Thank you in advance.
Seems you are installing TFS 2010 to simulate some existing environment and test configuration changes. However, there is not any setup.exe for TFS 2010 in official site for now.
It's unsupported and 8 years old. There have been five major releases since then. We encourage users move to newly version of TFS server. Either back up the TFS2010 database and do the move directly or use some other machine with DVD to install the TFS2010 ISO image for a test.
We are having compilations problems in a TFS server and it's because the server lacks several libraries built in the default VS2012 Premium installation (Microsoft Fakes in this case).
I'm unsure of going ahead installing a full instance of VS, but first I want to know what is the best practice in this regard?
What is recommended?
Since we are talking a sandbox, do whatever and don't worry about it. If we are talking best practices, it's not a good idea to put your build tier on the app tier / data tier. Any developer could check in code that gets run on the server during the compile and trash your entire environment.
Have you looked at Visual Studio Online? It's a hosted TFS service and you can use their hosted build controller or configure your own. That makes for a very good sandbox IMO.
I don't see any issue installing VS on the TFS server(I assume you run your builds on that server too and that's when you are seeing the problem. Ideally tfs server and build box should be separate but some people use the same box.)
I have used Visual Studio on the build box several times to debug issues with builds. You just need to make sure you close the VS instance (if it has a solution open) once you are done with debugging otherwise your builds can fail when they try to clean up the project directory at the start of the build.
We run a single server TFS instance which has everything - sql, SharePoint and tfs - running on it. It is also a build server so it has to have VS 2010 and 2012 installed. We've done this with all versions since 2005 and have had no issues with it at all.
I cannot create a new SQL Server Database Project on my machine that have installed Visual Studio 2012 Ultimate and SQL Server 2012
I got the below error saying that the SQL Server runtime components not matched.
Do you have the same issue? And what is the work-around for this?
You need to download the latest version of SSDT from http://msdn.microsoft.com/en-us/data/hh297027 (or by clicking the "Get the latest version" link in the error message). SSDT uses a shared component called DacFx, and when you installed SQL Server 2012 on your machine a newer version of DacFx was installed. Updating SSDT will ensure everything is compatible.
Note: Make sure you have a stable internet connection, otherwise you may have issues installing from the web installation and/or the .iso file download.
ISO file download is the problem. This is the second time I have seen the ISO image from MS website has this problem in 1 month. Some are corrupted there are no such files like ".be" prefix "." + file name. Bad file name caused everything.
I've installed Firebird NETProvider and DDEXProvider on Windows 8 Enterprise (64-bit) with Visual Studio 2012 Premium successfully: I added a connection in Server Explorer and was able to see the database-objects.
However, when I install other extensions (Web Essentials, Power Tools, Resharper) I loose my previously saved connection and I'm unable to re-create it, because the Firebird NETProvider is no longer available. The same result after installing Windows updates (KB2781514), concerning a fix for VS2012.
Re-installing the NETProvider and DDEXProvider causes problems in the VS-configuration (double entries of dataproviders, etc.).
I'm unsure in using the Firebird NETProvider in a project with legacy Firebird-database) , because it seems to be unstable in VS2012.
Hopefully someone can help me.
Many thanks in advance
Dirk Schelfaut
I had the same problems after installing VS 2012 SDK. Solution: Click the Advanced button in the installer and verify whether the correct combination of VS and OS is checked. With my installation, VS 2012 (64 bit OS) was checked, but I had W7 32 bit... You also may have to check the machine.config file. After re-installing, I had several duplicate entries for the Firebird data provider. Regards, Ulli.
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.