Whenever I export a data tier application from my Azure Sql Database and then Import that .bacpac file from that export into my local Sql Server after the machine is restarted the database is marked as suspect. Before restarting the machine the database works great, but after it is in suspect mode and I've not been able to get it out.
Machine Information:
Windows 10 (19044)
Sql Server Express 2016
Related
I have a db in sql server 2014 and i am trying to deploy the database to Azure db using Tasks-> Deploy database to Azure SQL Database.
I installed DAC framework but still i am not able to. When i try to connect to my local Azure server from SQL Server i am able to connect to it. Is there anything else that i am missing ?
Keep in mind that Azure SQL PaaS was quite immature in 2014.
Please upgrade your SSMS version to 17.x. This will work fine with your SQL 14 databases but have all the upgraded tooling for Azure SQL included.
Actually we have Azure SQL Management instance I got a backup but I cannot restore our VM SQL Server owing this has a SQL Server version less SQL Azure (Azure Team updated SQL Server a couples week ago), so We cannot update QA Server to last SQL Server Version and we need to recovery the backup a soon a possible.
Do you know any way to recover this backup from SQL Azure to this server getting a less version?
Thank you!
You can also use bcp to export the data from Azure SQL Database and then use bcp again or Import/Export Wizard or SSIS to import the data on the SQL Server VM.
You can use Azure Data Factory (ADF) to export tables to your SQL Server VM. ADF will create those tables and copy the data.
I installed SQL Server 2017 Express as a named Instance alongside my default instance. After rebooting once - both were showing but the I could not connect to SQL Server Express remotely. I then followed the instructions to enable IP on SQL Express using configuration manager and rebooted. Now I can connect remotely but my default instance is showing NO databases!
Also in configuration manager, SQL Server Services does not show any of my instances so that I can check they are running (this was the care even prior to enabling the IP address on the protocol, and when I knew it definitely was running as I could connect to it)
--
Update:
I discovered if I launch SQL Server Configuration Manager 2016 rather than "SQL Server Configuration Manager" I can see all my servers.
SQL Server 2016 appears to be running as is SQL Server Express. There is also a "MSSQLServer" that is stopped - think this may be SQL Server 2012. Not sure at this stage which one had the databases.
Ok so for anyone in a similar situation / panic. Do the following.
Look to see what other SQL Server configuration mangers are showing up. If you have installed multiple versions over the years chances are you'll see more than one.
Try using one of the later ones. You can see the file path too if you need it here.
If you manage to see a list of your database servers, check which are enabled and disabled. I had to disable SQL Server (SQLExpress) first before I could enable SQL Server (MSSQLServer), which in my case referred to SQL Server 2012.
If you want to have SQL Server Express running as a named server running alongside your default server, make sure you assign it a different port number (e.g. 1435) in the SQL Server Network Configuration>Protocols for SQL Express>TCP/IPALL section in SQL Server configuration manager.
I exported a bacpac from Azure SQL Database and am trying to import it on my local environment.
It works perfectly on my development machine running SQLServer 2016, but if I try and install it on a server running SQLServer 2012, I get a compatibility issue.
'A project which specifies Microsoft Azure SQL Database V12 as the target platform may experience compatibility issues with SQL Server 2014'
It is definitely not any of my stored procs/tables etc as it is not using anything specific to newer SQL databases.
I am using the latest SSMS and have also tried installing some of the Data Tier application hot fixes that some people have mentioned, but no joy.
I'm trying to export a DB from my local SQL Server to Azure SQL.
So far I've tried
Tasks > Deploy Database to Windows Azure SQL Database
I then connect to the Azure DB, give the new DB a name and then let it run.
However, it fails with the message
A project which specifies Microsoft Azure SQL Database v12 (Preview) as the target platform cannot be published to Microsoft Azure SQL Database.
Having followed this page, I'm pretty sure that I have the latest of whatever I need on my local.
So what am I missing? How do I get a DB from a local instance of SQL Server to Azure SQL?
Although there are several means to upload a local DB to Azure, I found that all but one of these fails with the same error message.
The one which worked is the SQL Database Migration Wizard.