I have a microsoft sql server 2014 instance with a database "myDB". In SSMS I have registered this database as Datatier application. I have installed the latest dacfx with nuget to my visual studio project. When I hit DacServices.GenerateDriftReport("myDB") it throws:
Databases registered as a DAC database must be hosted by an instance of SQL 2005 SP4, SQL 2008 SP2, SQL 2008 R2, SQL 2012 or SQL Azure.
Also the method DacServices.Unregister throws this error.
I am installing Windows Server Updates to the SQL Server machine but I don't believe this would fix it.
Related
I installed SQL server management studio 2020 now it’s not connecting
even I tried to start the SQL services but I didn’t find SQL services in services.
We restored our TFS 2013 database backups on separate data tier with SQL Server 2012. Now I am trying to add these databases to TFS server (it's a sandpit tier), where I have a SQL Server 2008 R2 version. While running app tier wizard, I added SQL instance but it is throwing an error:
TF400860: the current version of following service is not supported registry Version 5, min version 5
Both servers have same version of TFS (TFS 2013.5)
Can anyone advise how to fix this?
The minimum SQL version for 2013 is SQL 2012 with SP1 https://www.visualstudio.com/en-us/docs/setup-admin/requirements
The minimum SQL server requirement for TFS 2013 is SQL server 2008 R2 (SP1).
The solution for this error is, we need to change the SQL server instance availability group as primary by logging in to same server
We have 4 data tiers, which are in sync, I tried it and I got it with SQL version 2008 R2. No need of SQL version 2012 or higher.
Thanks
Currently I am creating SSIS packages for SQL server 2014 using Visual Studio 2012 and the SSDTBI for VS2012.This works well.
But I found some compatability issues with VS2012 for SSIS 2014(on web).I'm new to SSIS.I dont know what is that exact issues with VS2012?.And also they mentioned SSIS 2014 is compatible only with VS2013.Here i have mentioned the link below.
http://www.stefanjohansson.org/2015/02/issues-upgrading-an-ssis-solutionpackage-from-visual-studio-2012-to-vs-2013/
http://blogs.technet.com/b/dataplatforminsider/archive/201
3/11/13/microsoft-sql-server-data-tools-update.aspx
Can anyone tell me what is exact compatability issues for VS2012 with SSIS 2014?.I can not seem to find anything on google.
Thank you
According to msdn it possible.
On an instance of SQL Server 2014, you can import packages from an
instance of SQL Server 2008 or from an instance of SQL Server 2012,
but you cannot export packages to an instance of SQL Server 2008 or to
an instance of SQL Server 2012.
-
Run packages. You can run SQL Server 2008 Integration Services and SQL
Server 2012 Integration Services packages by using the SQL Server 2014
version of the dtexec utility or of SQL Server Agent. Whenever a SQL
Server 2014 Integration Services tool loads a package that was
developed in SQL Server 2008 or SQL Server 2012, the tool temporarily
converts, in memory, the package to the package format that SQL Server
2014 Integration Services (SSIS) uses. If the SQL Server 2008 or SQL
Server 2012 package has issues that prevent a successful conversion,
the SQL Server 2014 Integration Services tool cannot run the package
until those issues are resolved. For more information, see Upgrade
Integration Services Packages.
However, I would just use VS 2013 if you can.
I have a Windows forms application targeting .NET 4.5. The application provides functionality for programmatic database backup and restore using SQL Server Management objects (SMO).
The application should support Express editions of both SQL Server 2008 R2 and SQL Server 2012 as its using only features that are supported in both versions.
Now the SMO assemblies (Microsoft.SqlServer.ConnectionInfo, Microsoft.SqlServer.Smo, Microsoft.SqlServer.SmoExtended etc.) to reference in the project will be in different folders depending on the version of SQL Server the client has installed
SQL Server Express 2008 R2: C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies
SQL Server Express 2012: C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies
As you can see, when the client is running 2008 R2, the assemblies will be down the 100\SDK folder while for those that want to run SQL Server 2012, they will be in the 110\SDK folder.
So if I reference the 100\SDK folder, the application will break for clients running SQL Server 2012 because they will only have the 110\SDK folder.
So how is such a scenario normally handled?
If you want to develop an application that uses SQL Server Management Objects (SMO), you should select the Client Tools SDK when you install SQL Server.
To install the Client Tooks SDK without installing SQL Server, install Shared Management Objects from the SQL Server feature pack.
If you want to ensure that SQL Server Management Objects is installed on a computer that will run your application, you can use the Shared Management Objects .msi in the SQL Server feature pack.
Source: Installing SMO - SQL Server 2012
Going by the underlined paragraph, I guess I can always install a common Shared management objects msi across client machines irrespective of sql server version being run.
I have SQL Server 2008 and VS2008 installed on my computer and I am trying to run a web application I've created on a computer which has SQL Server 2008 and VS2008 and VS2010 beta 2 with its SQL Server Express.
I am getting an error with the database version that is
"...aspnetdb.mdf" cannot be opened because it is version 655. This server supports version 612 and earlier...."
Configuring the database in Visual Studio ->Tools -> Options -> Design-Time Validation Database is not working since I don't have the SQL Server version comes with VS 2010.
EDITED : I also edited aspnetdb and inserted a few more tables so I need the same aspnetdb
Is there any solution to convert this db ?
Also, after fixing this, I am looking forward to upload it on my hosting which has SQL Server 2005 DB and configure it in PLESK.
The SQL Server databases have a version specific format. Each SQL Server runtime version (SQL 2008 SP1, SQL 2008 RTM, SQL 2005 SP2, SQL 2005 SP1, SQL 2005 RTM etc) knows how to upgrade to its own verison. Unfortunately, once upgraded the database cannot be downgraded. So if your MDF was upgraded to version 655, it cannot be downgraded to any prior version. If you know you're going to deploy on SQL Server 2005, you must develop on SQL Server 2005 too. Not only that, but the actual build number of your development has to match the build number of the deployment (or at least be lower than that): the SP level and CU level must match.
You can a attach the 2008 version MDF you created to a SQL Server 2008, script out the database content, then import the script into a SQL Server 2005 database of the proper version.
I had this problem and when I changed my_computer_name\SQLEXPRESS with . to connect to server and it works and I could attach MDF file
may be you have both services run. (Mssql2008 and mssqlexpress) Maybe you have runing the mssqlespress running, that's the error that you have. Try to stop the mssqlserver express service and run mssql2008 services, and attach again your databases. I try this and works for me