Database Restoration Error In Azure

Hi Friends,

(Started watching some more series after ending of Prison Break. GOT & Friends are among few of them.)

Today I would like to share the following error, while I was trying to restore bacpac file from one Azure Server to another Azure Server.

Requirement: There was a need to restore the bacpac file from one environment to another.

What I did was:

1 Took the backup (bacpac) file from one server.

2. While I was restoring it, it was throwing the below error:

3. After doing some research, got to know something new, that we have to install “SQL Server Data Tools”. Below is the link to download the file:
http://msdn.microsoft.com/en-us/jj650014

4. Once it was installed, we were through the restoration process.

Thanks for reading the article. Stay Tuned.

How to create Database and Migration in SQL Azure

Hi Friends,

As we have seen the welcome note on “SQL Azure” here. This is just a continuation of that post.

Here we’ll see how to create a Server, Database as well as how to authenticate the user to access the Database in Azure.

1.       Connect to windows.azure.com.

2.       Click Subscription >> Then “Create”.

3.       Select the location (Region where you wanted to deploy your Azure Database).

4.       Create Admin Login ID & set the password.

5.       Check “Allow other windows Azure services to access this service”.

Add the list of IP’s which can able to access the server.

6.       Click “Finish”.

Once it is done. A server name will be created, which one can use to connect and create a Database.

How to create Azure Database:

1.       Once the server is configured, connect to the server. Here we can able to see only “Master” Database (Master Database is not chargeable).

2.       Under Database >> Create >> Database_Name >> Select “Edition”.

3.       Database is created.

How to migrate Other Databases to Azure:

1.       If you are planning to migrate any other RDBMS to Azure, we need to first migrate it to MS SQL 2008 then only we can migrate to Azure.

2.       Once we have migrated to generate script of Database using Azure Tool (Reason all the features are not supported if we generate the script from SQL Server).

3.       SQL Azure >> Migration Wizard >> Generate Script.

4.       Copy the script and run it to create Azure Database.

5.       Populate data using either SSIS or SQL Azure migration wizard

Max size of DB is limited to 50 GB. We can connect to windows azure portal to view the bill.

Note: Above points are my understanding from the session, there might be some flaws. Looking forward for your note to correct me if I’m wrong anywhere.   

Thanks for reading the article. Stay Tuned.

Introduction on SQL Azure

Hi Friends,

Last week I've attended a session on “SQL Azure”. So thought of sharing the key points on the blog for our all reference. Till before attending the session, it was just a word for me “AZURE” with zero knowledge on this technology (or rather my understanding was just limited to “it is something related to Cloud”).

Following are some points I’d like to share which I learned from the session:

i.    We can consider SQL Serve Azure (SSA) just like a SQL Server (SS) Version (Cloud version). 

     It is the light version of SS.

ii.   SSA is Scalable, HA, RDBMS and Secure.

iii. SSA runs only on “Windows Azure Platform”.

iv.  One can connect the server through Azure Portal as well as SSMS.

v.    SSA has two Editions. Web Edition and Business Edition with 5 GB and 50 GB DB limit     respectively.

vi.   Data can be migrated from any other RDBMS such as Oracle, MySQL, SQL Server, etc...

vii. Pricing is based on the Usage (DB Size). Large the DB size is more your billing would be.

Difference between SQL Server (SS) and SQL Server Azure (SSA):

1.  Only SQL Authentication is possible in SSA; whereas SQL as well as Windows Authentication is also possible in SS.

2.  While making login Azure does not allow login name like sa, admin, guest, administrator and root. There is no as such restriction in SS.

3.  No CPU, CAL licensing is involved in SSA like SS; rather billing is done based on consumption (More the DB Size more the bill will be).

4.  Since SSA is a light version many features are not present in SSA compared to SS.

5.  SSA table must have Cluster Index whereas it’s not compulsory in SS.

6.  Only Master DB is present in SSA on contrary Master, Model, MSDB & Tempdb is present in SS.

7.  Max size of DB in SSA is 50 GB; whereas in SS it’s in TB’s.

8.  Transaction should stay in single DB; whereas in SS it can run adhoc queries.

9.  As it is in Azure only TCP\IP protocol is supported; where as in SS it supports many protocols.

10. In Azure, Application cannot go down unexpectedly.

Guys this is just a welcome note on SQL Azure.  There are lots of things to learn in SSA. Will keep on posting as and when I‘ll have the content along with the necessary snapshots.

Note: Above points are my understanding from the session, there might be some flaws. Looking forward for your note to correct me if I’m wrong anywhere.   

Thanks for reading the article. Stay Tuned.