I had a Access database, since the database limit is 2 GB, I am planning to migrate to Azure Database. I need to upload data with the help of BCP but I was wondering how users will be able to use it since they wont have SSMS installed in their PC. Please help
Use either:
SQL Server Migration Assistant (SSMA) v7.3
or perhaps the new (still in preview):
SQL Operations Studio
Related
I am trying to create a free SQL Database in Azure under my DreamSpark subscription but I repeatedly receive the following error:
When you start an SQL Database creation, Azure lets you choose or create an SQL Server:
Since I don't currently have an Azure SQL Server I have to create one. I figured my error could be isolated to the server creation and effectively, while trying to create only the server, the error still rises.
I think that, even if Dreamspark subscription allows for a free small SQL Database, it does not allow for a free SQL Server. But this does not make any sense because I think there is no way to have an SQL Database without an SQL Server... So my questions:
Could you please confirm or refute my suspicion about Azure not permitting a free SQL Server in DreamSpark subscription?
In case it is not allowed, is there a way to create an SQL database without an SQL Server in Azure?
In case it is indeed allowed, why do I have this error then?
Thanks in advance.
I ended up circumventing this problem by using visual studio 2017 to create DB and DB Server for me. So we can be sure that DreamSpark subscription allows for a small DB AND a DB Server creation, which makes sense.
Still, don't know why I was getting that weird error though.
While creating the db, visual studio changed the name I provided by concatenating "dbserver" and "_db" to the server and db respectively. Perhaps, there was a naming issue that VS solved automatically, and that Azure is not reporting correctly.
I have an Oracle DB with data that I need to load and transform into an Azure SQL Database. I have no control over either the DB nor the application that updates its data.
I'm looking at Azure Data Factory, but I really need data changes in Oracle to be reflected as near to real-time as possible.
I would appreciate any suggestions / insights.
Is ADF the correct tool for the job? If so, what is a good approach to use? If not suitable, what should I consider using instead?
For real-time you don't really want an ELT/ETL tool like ADF. Consider a replication agent like Attunity or (gulp at the licensing costs) GoldenGate.
I don't think Data Factory is not good for you. Yes you can copy data from Oracle to Azure SQL database with it. But like #Thiago Custodio said, we need need to do it to each table you have. That's too complicated.
Just reference: Copy data from and to Oracle by using Azure Data Factory.
As you said, you really need data changes in Oracle to be reflected as near to real-time as possible.
The migration/copy time must be very short. Then the data in Oracle and Azure SQL database could be same before the Oracle data changed next time. I searched a lot and didn't find any real-time copy tools. Actually, I think you want the copy could be something like 'data sync'.
I found this link Sync Oracle Database with SQL Azure, hope it could give some good ideas for you.
About the data migration or copy, You can using bellow ways:
SQL Server Migration Assistant for Oracle (OracleToSQL)
Azure Database Migration Service (DMS)
Reference tutorial:
Migrating Oracle Databases to SQL Server (OracleToSQL): SQL Server Migration Assistant (SSMA) for Oracle is a comprehensive environment that helps you quickly migrate Oracle databases to Azure SQL database.
How to migrate Oracle to Azure SQL Database with minimum downtime:
Hope this helps.
For the record, we went with a product named QLik Replicate (aka Attunity) and it is working very well!
I have a few questions regarding upgrades/downgrades of azure sql. The only information I found was that to upgrade/downgrade you have to export a .bacpac and import it on a new upgraded/downgraded server.
Does Microsoft "force" you on to newer versions of azure sql when they are available?
How do you upgrade your current azure sql version?
How do you downgrade your current azure sql version?
There is a SQL server versión property on the Azure SQL Server créate request (reference). The DB created on that server will just inherit that versión.
As for your question:
Probably at some point in time it might, not that it happens often. This happened once (as far as I recall) and I dont remember if they forced you to migrate or not, probably did at some point.
Create new server, Backup\Restore databases
Create new server, Backup\Restore databases
I dont think points 2 and 3 have any real application in the current state of affairs, since Azure SQL is almost locked to v12 (which isnt equivalent to SQL 2012), I can hardly imagine a case where you would want to downgrade (and there's no room to upgrade).
My website is a .net 4.5 mvc site built with VS 2012. I have a SQL Server Compact DB in my app_data folder. All works great on my localhost. I deploy to Azure website and get this error?
Unable to find the requested .Net Framework Data Provider. It may not be installed.
I've googled it and get lots of possible answers, but none specific to Azure and SQL server compact. So my question is simple. Does a windows Azure Website which is deployed to an Azure shared hosting server support SQL Server Compact? If so, what do I need to do to eliminate the aforementioned error and make it work?
It certainly is possible to use SQL Server Compact on Windows Azure. However, you need to ask yourself:
Will I change anything in database?
This includes adding, updating and removing data. If you do, you should not use SQL Server Compact on Windows Azure. Because, if you use SQL Server Compact on Windows Azure and change anything in the database, you'll run into two problems:
Data is not replicated.
You risk losing data.
Data is not replicated
If you change anything in the database, the changes stays local. This means that if you have multiple instances running your web application, then each web application will have their own database, and if you change something in one of them, the change won't be replicated to other instances, which will result in unpredictable behaviour in your application.
You risk losing data
If you change anything in the database after deployment, you risk losing data, because Windows Azure might decide to redeploy your instance to another virtual or physical machine. When this happens, the new instance will be setup with the deployment package you originally uploaded to Windows Azure, and this package does not contain any changes you make to the database. And this redeployment can happen at any time for several reasons.
Conclusion
So, SQL Compact on Azure? Sure, no problem if your data is read-only. However, note that you won't get the performance you would with SQL Azure. But if your need changes down the road, you can always migrate your application from SQL Server Compact to SQL Azure.
If you want to use SQL Server Compact with Windows Azure, you can use the "private deployment" method, as explained on "ErikEJ"'s blog.
Edit: Microsoft has announced that they now provide 1 free 20 MB SQL Azure Database for every Azure subscription. This means you can create a subscription and create a free website, with a free SQL Azure Database. (As long as it's less than 20 MB) You can also have multiple Web Sites associated with the same SQL Azure Database for free. So, if you're considering SQL Server Compact on Windows Azure because your database will be very small and you don't want to pay for a 100 MB database, you can consider this option. In most cases, it will be a better solution. Your website will perform better, your database performance will be better and you have the ability to change your data and it will be replicated.
It's possible for SQL Server Compact 4.0 on Azure!!
I write an an article for it
And this is the English version I found
By few step:
Below is the solution after my research:
Step by Step like this:
Install two nuget: EntityFrame.SqlServerCompact & Microsoft SQL Server Compact Edition
put your SQL database file(.sdf/.mdf) in APP_Data folder
(Put the connection string like this in order to use it:
<add name ="DefaultConnection" connectionString ="Data Source=|DataDirectory|CompactDB.sdf" providerName ="System.Data.SqlServerCe.4.0" />)
Publish full project include above SQL database file to AzureWebsites.
you can find it can work well and is totally free.
Second Wenchao Zeng of Microsoft the Azure don't support Sql Compact.
I could use once but this is not recommended because the Windows Azure work with replication of the data (this is the cloud, remember?) and the Sql CE does not support this functionality. If you can to put a Sql CE in Azure sometimes will not get access or users see data outdated or broken because the async.
The best way is you to use the Azure Sql ou BLOB storage.
What's the best way to move a normal SQL server database to SQL Azure? Is it right that you can't restore from a backup file? The only way I've found so far is to script the database (and its data) and run those scripts on the SQL Azure database but this is slow when you have lots of data.
Use the SQL Azure Migration Wizard if running SQL 2008: http://sqlazuremw.codeplex.com/
For older versions the best thing I've seen is to either first upgrade to 2008 then port, or (unfortunately) to port the data using scripts as you've suggested. If you have to do so, might I suggest SubSonic for generating your scripts?
Patch SQL Management Studio 2014 with the latest patches
Connect to your onsite sql server
Right click Database > Tasks > Deploy Database to Windows Azure SQL
DONE!
Thank you:
http://blogs.msdn.com/b/brunoterkaly/archive/2013/09/26/migrating-an-on-premises-sql-server-2012-database-to-windows-azure-sql-database.aspx
Use the SQL Azure Migration Wizard if running SQL 2008:
http://sqlazuremw.codeplex.com/
https://code.msdn.microsoft.com/The-best-way-to-migrate-6c4a7326
Be warned, backup your local copy before attempting SQLAzureMW. If the BCP entries aren't just right, it will target your local DB instead of Azure. Just recently had SQLAzureMW v3.3.9 successfully create tables on Azure, but (re)load the data (rows) in the source (local) DB.
Use:
SqlServer DataBase > Task > ExportData > Source > Destination
All Done..
Use Microsoft Data migration assistant tool which can be downloaded from here. https://www.microsoft.com/en-us/download/details.aspx?id=53595
First you have to install it. By using the Azure portal create new SQL database.Now you can deploy your local SQL database into Azure SQL database. If you have some warnings at the end of the migration process please ignore it.