I an trying to migration tables from a MS Access database (local drive) to SQL Azure. The issue is that when I select the access database SQL Server Management assistant shows 0/0 tables. I can open the database locally and there are 8 tables. Not sure why SQL Server Migration Assistant does not see any of the tables in the access database.
I am using version 6.0 of SQL server Migration Assistant.
I am not sure if you checked the resource here about preparing the access database for migration. It is possible that there are some incompatible features or settings in the Access database that is preventing SSMA to work.
Are there any error messages in the log file? You can find it at "%APPDATA%\Microsoft SQL Server Migration Assistant\Access\log\ssma.log". Can you post any relevant information here?
Related
I am migrating my databases from Azure SQL VM to Azure SQL DB using offline migration but while migrating I am getting a error i.e " Microsoft.Azure.Management.DataMigration.Models.ODataError"
I am using powershell script to migrate the database.
I don't know what is wrong in this and why am getting this error.
I have attached the error screenshot herein.
As per this thread on Microsoft Q&A, the issue could be in relation to different collation on the source and destination DB's. I recommend you to raise a support ticket if possible.
Alternatively, you can use SQL Server Management Studio(SSMS) to migrate the Database.
Install the SSMS in your local machine and connect to the Azure SQL VM by following connect to SQL server steps in the tutorial.
Once you are connected with the server, follow the steps as mentioned in this thread to migrate the database to Azure SQL Database.
I am connecting to an Azure hosted SQL Server using SSMS and am getting an error I can't track down. This happens when I open the connection and try to select a database to use or try to refresh the database list.
Reference to database and/or server name in 'msdb.dbo.syspolicy_configuration' is not supported in this version of SQL Server.
For the best experience with Azure SQL Database please download for free the latest version of SQL Server Management Studio (SSMS). Please download it from here.
The latest version of SSMS is compatible also with SQL Server 2008 and later.
SSMS 2012 is not compatible with many changes and improvements Azure SQL Database has received the last 6 years.
I have a backup of a SQL Server 2008 database. I'd like to restore it as an Azure SQL Server database. Is this possible?
P.S. I've seen a couple of questions to this effect from 2014. Is it possible today?
AFAIK, no it's not possible.
The Unsupported in SQL Azure doco https://azure.microsoft.com/en-us/documentation/articles/sql-database-transact-sql-information/ directs you to BOL and RESTORE shows it's not available in SQL Azure.
https://msdn.microsoft.com/en-us/library/ms186858.aspx
Are you able to restore the backup to an instance of SQL 2008 on-premises/locally first? If so you can then use management studio to Export the data and schema as a BACPAC or DACPAC file (export data tier application), which can then be imported into an Azure database using the Import data tier application. You can also use the Taks -> Generate Scripts option from the database node in the management studio, ensure you check on include schema and data - then the SQL files can be executed against your SQL Azure instance as well.
There are some features which aren't available in SQL Azure that are on the server product, but the import will tell you about those if there are any - things like FILESTREAM aren't supported in Azure. Here is the link to take you through steps to migrate from SQL server to SQL Azure - and here are the differences in supported features between the two.
I have some production databases in Azure and frequently download them as data tier apps, import them into a local instance of SQL Server to do some debugging or testing, its a painless process.
Recently, I purchased a licence for a Microsoft Azure SQL Server 2012 (packet "S0" - Standard, 250 GB)
When I connect with SQL Server Management Studio 2012 to this database, then all the user interface dialogs for creating tables, setting up users, etc. are gone.
You can only script and execute pure SQL statements.
Even the table editor is gone, so you even cannot edit the data in a table!
If I connect to a local database, then everything works. So the problem must be related to the Azure Database. Can anyone help ?
If this is Azure SQL Database, then keep in mind that this is not the same as SQL Server 2012 although you can use the same tools to connect to it. This behavior is therefore correct and normal. If you have installed or used an image for SQL Server on a VM then you should have everything as you expect.
I am trying to create a .bacpac file of my SQL 2012 database.
In SSMS 2012 I right click my database, go to Tasks, and select Export Data-tier Application. Then I click Next, and it gives me this error:
Error SQL71564: Element Login: [myusername] has an unsupported property IsMappedToWindowsLogin set and is not supported when used as part of a data package.
(Microsoft.SqlServer.Dac)
I am trying to follow this tutorial so that I can put my database on Azure's cloud:
http://blogs.msdn.com/b/brunoterkaly/archive/2013/09/26/how-to-export-an-on-premises-sql-server-database-to-windows-azure-storage.aspx
How can I export a .bacpac file of my database?
SQL Azure doesn't support windows authentication so I guess you'll need to make sure your database users are mapped to SQL Server Authentication logins instead.
I found this post referenced below which seems to answer my question. I wonder if the is a way to do this without having to delete my user from my local database...
"... there are some features in on premise SQL Server which are not
supported in SQL Azure. You will need to modify your database before
extracting. This article and several others list some of the
unsupported features.
This blog post explains how you can use SQL Server Data Tools to
modify your database to make it Azure compliant.
It sounds like you added clustered indices. Based on the message
above, it appears you still need to address TextInRowSize and
IsMappedToWindowsLogin."
Ref. http://social.msdn.microsoft.com/Forums/fr-FR/e82ac8ab-3386-4694-9577-b99956217780/aspnetdb-migration-error?forum=ssdsgetstarted
Edit (2018-08-23): Since the existing answer is from 2014, I figured I'd serve it a fresh update... Microsoft now offers the DMA (Data Migration Assistant) to migrate SQL Server databases to Azure SQL.
You can learn more and download the free tool here: https://learn.microsoft.com/en-us/azure/sql-database/sql-database-migrate-your-sql-server-database
As of 9/2018, there is a new tool called the Data Migration Assistant that can help with the task of migrating an existing on-premise SQL Server Database to Azure. While the tool will NOT resolve the issue of migrating Windows Logins, it will at least help you get your database schema and data migrated up to Azure.
Here is the overview of the tool: https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-2017
You can download the Data Migration Assistant here:
https://www.microsoft.com/en-us/download/details.aspx?id=53595
Once you have migrated your database up to Azure, you can configure an AD Administrator on the SQL Server, then create contained users in your database to allow users to login to your SQL Database with their Windows accounts.