I am using Visual Studio 2010 and want to use SQL Server 2008 as a backend. I successfully installed SQL Server 2008 and configured it. It is even getting connected in Visual Studio 2010 unless I am trying to create a database for an particular project.
It's causing an error:
Failed To Generate User Instance Of SQL Server Due To A Failure In Copying Database Files.The Connection Will Be Closed.
I searched and found one solution stating to delete Microsoft SQL Server data folder in user-appData... But still problem is there. What can be done to solve this issue?
I'm attempting to use SSDT to publish to a SQL Server database in Azure. When I do so, I am seeing the following error:
Unable to connect to master or target server 'DATABASE_NAME'. You must have a user with the same password in master or target server 'DATABASE_NAME'.
Ignoring the fact that it's listing a database name as the server name in the error, I'm not sure how to resolve it. When I specify the target database, I can successfully Test Connection. I can also connect using the same creds to the database through SSMS.
After researching the error, it seems like it is often that the firewall for the database in Azure does not include the IP address of the machine you're publishing from. It not only contains my IP, but I added another firewall rule to allow every IP (0.0.0.0-255.255.255.255) to eliminate the firewall as a potential cause of the problem.
Any ideas?
This is a known issue. This happens due to the new compatibility level 140 for newly created SQL Azure databases. The issue has been documented here and updating SSDT from here to the latest version may solve the issue.
Alternatively, you can change the compatibility level of your database to 130.
ALTER DATABASE database_name
SET COMPATIBILITY_LEVEL = 130;
Hope this helps.
Initializing deployment (Start)
Initializing deployment (Failed)
*** Could not deploy package.
Unable to connect to master or target server 'DbName'. You must have a user with the same password in master or target server 'DbName'.
Issue occurred while deploying build through VisualStudio-2015 and it support to publish database on the database servers whose version up to only 2016.
Solution: For SQL server 2017 we need to Publish Database with Visual Studia 2017 only. Need to upgrade SSDT.
Faced same issue when trying to deploy a DB from local SQL Server to Azure SQL DB via SSMS.
Tried to alter source DB's compatibility level to 130, still got same error.
Tried to add same user logins to master DB, no help.
Eventually, started looking for other approaches. Succeeded by using Data Migration Assistant, as instructed in https://learn.microsoft.com/en-us/azure/sql-database/sql-database-cloud-migrate.
My situation was slightly different in that I had exported an Azure database (with compat level 140) from SQL Azure and then tried to import it into a local SQL Server 2017 installation - using the latest SSMS 2017 that I just installed yesterday - and still got this message.
Turned out that although I did have latest SSMS installed, I was actually opening SSMS 2016 by mistake! So be sure to select and pin the correct version to avoid it happening again. Just typing 'SSMS' into the Windows Start menu may not show both.
So if you use SSMS to import you only need the latest version, and no separate tools.
Footnote: Even after opening the correct SSMS version I got another error - something about contained databases.
An Azure database is a 'contained' database (or at least mine was) - meaning that its user logins are embedded in the database. This isn't enabled by default apparently in standard SQL Server 2017.
After running this in the local SQL in master I was able to import it successfully.
sp_configure 'contained database authentication', 1;
GO
RECONFIGURE;
GO
When this happened to me it was due to the version of tools I was using. I thought it strange that the most recent SqlPackage.exe I found in C:\Program Files (x86)\Microsoft SQL Server didn't work and publishing from visual studio did, so I found the most recent
under the visual studio directories:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\SQLDB\DAC\150\SqlPackage.exe
* to publish to a SQL Server database in Azure*, you can use "Data Migration Assistant" (DMA).
I just tried it and it works smoothly without any issues (firewall and compatibility level)
please refer to this link SQL Server database migration to Azure SQL Database
for step by step: 10. How to migrate the SQL database to Azure with the Azure Database Migration Service
I got the same error while trying to update a local SQL Server database from Visual Studio database project (i.e. not i Azure). Turns out the problem was I was running SSDT for Visual Studio 2017 while using Visual Studio 2015. Visual Studio discovered an updated version of SSDT (just happened to see it in notifications!), pointing to the right Visual Studio version. Now it works!
My setup: BizTalk Server 2016 forces me to use Visual Studio 2015. My local database is on SQL Server 2017. Using SSDT for Visual Studio 2015 works for updating databases in SQL Server 2017. Just so you know. ;)
Most of the sources recommend to set COMPATIBILITY_LEVEL = 130; and, usually, it solves the issue. Unfortunately, this did not help me.
In my case, I had to downgrade SQL Server 2017 on my machine to SQL Server 2016 Developer Edition.
I ended up having to install DacFramework.msi on the SQL server that my azure runner agent was installed to get past this error. My server is a VM running in our network. not running in azure...
the description on the msi says:
'This installer database contains the logic and data required to install Microsoft SQL Server Data-Tier Application Framework (x64).'
Try to connect to the SQL Azure database using Sql Server Management Studio and the ip getting listed in the management studio is the right ip address. Try to add to the SQL Azure firewall rules. The ip address listed in the firewall page of Sql Azure portal is not accurate.
I am trying to install TFS 2013 on a server that previously had TFS 2015 installed, then removed.
When the process runs, there are a number of databases it can find, that need to be removed. I have removed these, but it is saying there is still one database: Tfs_Analysis.
I have looked in the server and I cannot see the database in the list of databases. I have full permissions on the server, so it is not a case of it being there and I cannot see it.
What is really confusing me is that SQL Server will allow me to create a database with the same name and remove it.
I have restarted the SQL Services and have also restarted the server. Can anyone suggest what I am missing?
When you connect to the database from SQL Management Studio, choose Analysis Services as the server type
Now you should see Tfs_Analysis under the list of databases and you can delete it so the TFS 2013 setup doesn't give you any trouble
I'm in the middle of what Microsoft calls an advanced TFS 2013 installation on new hardware. I want to point it at my current database running TFS 2010 on a different server and wanted to know if I can do this or if there are any tools available to upgrade the existing database.
I upgraded the SQL Server running the TFS2010 databases to SQL Server 2012 and can connect so that is not an issue. I'd like to keep the same databases for obvious reasons and could not find any info on a road map to do so.
Anybody have any insight?
Thanks.
Just in case anyone comes in here and is looking for an answer. It is possible to install TFS2013 on one box and point to databases that were created in TFS2010, but those databases must be converted to SQL Server 2012.
What I did was to upgrade our SQL Server from 2008 to 2012 and the tfs databases were still accessible to users on tfs 2010. Then you go to the tfs 2013 administrator and attach a collection. You put your server name into the available servers edit control and you'll see your project collection database. The first part of the attach process is an evaluation and if something bad happens, at least it's in the analysis phase. Make sure you have a database backup and then click through so that the operation starts.
After the database is attached through tfs, you have some work in sql server to do. First detach the collection in tfs 2013. Then, in sql server, backup the project collection database again and copy it to your new tfs 2013 server running sql server. Then, again in sql server, detach the database.
Then go back to tfs 2013 and in sql server restore from the backup you created. Once that is done, in the tfs 2013 interface attach the collection and you're good to go.
Hope this helps.
I've been working on this ASP.Net Project for a few months, and today my SQL Server 2012 Management Studio has expired. Completely overlooked that i may have been using a trial version and not the express edition. I can not access SQL management studio as it says the evaluation has expired.
Is there a way i can downgrade to the express edition (Free), without losing any databases?
Is there a way i can still backup/export the database i have been working on? Ive tried using the import/export 64 bit tool, but ive forgotten my sql server password. I had just been using the default all this time.
Thanks
Backup database: You can get close backup of your databases by copying the data and log files from your Data directory. You can do this just using Windows copy and paste command.
Re-install from trail version: I faced this problem for SQL Server 2008 trial version. When SQL Server 2008 expired, I was able to re-install it as follows:
a) Remove or uninstall all tools of SQL Server completely from Control Panel > Programs and Features.
b) Then, re-install SQL Server as a new fresh tool.
c) After completing the installation successfully, Cope and paste those backup data and log files into new data directory of new installation.
d) Open SQL Server Mgmt Studio and attach the data file to re-create your old database. Your database will be resumed in this way.
I believe you can do this procedure for your SQL Server 2012 trial version too.