Import and Export (CTP) is an interesting SQL Azure feature that allows us to Export a SQL Azure database in form of a bacpac to Azure storage. And think of bacpac as the “zipped” version of schema and data in your database. It also allows us to import the bacpac to a SQL Azure database….Read more on SolidQ Blog: Step by Step guide to Export a SQL Azure Database to Azure storage via Import and Export CTP
Let’s say you have signed up for a SQL Azure free trial and it allows you 1 web edition database of Max Size 1 GB for a Month. You want to make the best use of this resource to get the maximum out of it, don’t you? No worries – In this blog post, I’ll list tips and tricks which would help you get the maximum out of that 1 GB SQL Azure database in a given month.
One option is to install Adventure Works LT sample database for a month – you try connecting SSMS, run queries, create DB objects, run stored procedures and you realize that it is SQL server in cloud (SQL server vs SQL Azure) – And you used your 1 GB SQL Azure DB free trial for a month, fair enough – you did learn a few things and that’s good. Now, let me propose a slight change that will allow you to try features such as SQL Federations and SQL Data SYNC and still not go above the “free” usage limit.
Before I do that – it is important to understand this:
When you are given a 1 GB Web edition SQL Azure DB free trial for a month – it effectively means that you have “30” 1 GB web edition SQL Azure DB whose validity is one Day and this is so because – the SQL Azure billing is “on per day” basis.
Note: The billing cycle is based on UTC format and not your “local” Timezone.
Now let’s take this one step further:
This billing model allows you to create “30” 1 GB web edition DB for 1 day – and you have exhausted your free trial cap.
Alternatively, this allows you to create “15” 1 GB web edition DB for 2 day – and you have exhausted your free trial cap.
Alternatively, this allows you to create “10” 1 GB web edition DB for 3 day – and you have exhausted your free trial cap.
And I hope – you got my point that you can spread those “30” 1 GB web edition DB in many different combinations.
Now, here is one way you can go about o spread your cap of “30” 1 GB web edition SQL Azure DB:
|Number of Days
|Feature||Details||Number of 1 GB web edition DB consumed per day
[Col1 * Col4]
|5||– learn basics||– connect via SSMS
– run TSQL commands
– Explore Management studio
– SQL Azure firewall
|2||– Data SYNC||Learn cloud to cloud synchronization using 1 Hub SQL Azure DB and 2 Member SQL Azure DB||3||11/30|
|2||– Data SYNC||Learn Enterprise to cloud synchronization using 1 hub SQL server DB and 1 SQL Azure DB||1||13/30|
|2||– Azure reporting||Learn SQL Azure reporting||1||15/30|
|1||– COPY TSQL command||-copy a SQL Azure DB using COPY command||2||17/30|
|1||-SQL Azure Import/Export||Export a SQL Azure DB to Azure storage blob and then import it back to a new SQL Azure DB||2||19/30|
|1||– SQL server to SQL Azure migration||try various migration tools like SSIS, BCP, SQL Azure migration wizard to migrate SQL server DB’s to SQL Azure||3||22/30|
|1||– SQL Azure federations||When you SPLIT a SQL Azure DB, it will perform it ONLINE. that means a single split command equals two create db command and one drop command and so for that day – you are charged for three db’s. Read more here||5||27/30|
|3||– Anything you may want to learn||you have “3” db’s to learn any other feature||1||30/30|
Now, this is not the optimum plan but it does give an idea to plan your free trial usage. I’ll tell you why the above plan is not optimum. For instance, when you try COPY command – you have two databases to play with for the rest of the day and you can do bunch of stuff with it. Other being, Once you have migrated the local SQL server db’s to cloud – you have those db’s to play with for the rest of the day. (Again, a billing day is counted based on UTC format. be aware!)
So yes. This is it! you can tweak the above plan based on your need and time you may have. feel free to post your suggestions in the comment section.
Just learned is a section in the BeyondRelational site that is meant for members to post a nuggets (short) of knowledge. I like this section – and so time to time i open the section and browse through the posts and once in a while, contribute. Here is the list of tips that i submitted this year:
Windows Phone just ran one of the best klout perk ever! So the way it works is that based on the score on Klout (which is a service that measures your online influence) – some people including me were invited to a Windows Phone Launch Party and they were also gifted a Windows Phone.
Here’s my Gift:
And I was eligible for this perk as i am (as per klout) an influencer on Microsoft Technologies (in Dallas, Texas area).
Thank you Windows phone for a great party and gifting me a phone that i like a lot!
Part 1: We defined SQL Azure and discussed advantages of SQL Azure
Part 2: We created an Azure account and created our very first SQL Azure database
Part 3: We discussed about the provisioning and the billing model of SQL Azure
Part 4: We discussed the SQL Azure architecture
Part 5: We discussed the SQL Azure security model
Part 6: We discussed how to migrate Databases to SQL Azure
Part 7: We discussed how to improve performance of SQL Azure DB and options for planning backup and restore strategies.
Part 8: We discussed administrative tasks related to SQL Azure.
Part 9: we discussed about Developing SQL Azure applications.
Part 10 A: We discussed about SQL Azure Data SYNC and SQL Azure reporting
Part 10 B: Conclusion
1) you have never installed python platform before.
2) you are new to Google App Engine.
3) you are running windows. if you are running Linux – the process is different. And please refer this for getting started.
4) you have a Google account.
Ok. So let’s get started with developing a hello world python app on windows first and then upload that app to Google App Engine.
1. Get the python development environment for windows.
I opted for Active state python community edition which you can download from: http://www.activestate.com/activepython/downloads
2. Install Google app engine SDK for python.
The second step is to download the Google App Engine SDK for python on windows which you can download from: http://code.google.com/appengine/downloads.html
3. Create an Application on Google and get the APP ID.
Now, let’s sign up for a Google App Engine Account with a Google account you may have. Part of the process includes verification via a code sent to your mobile device – so be ready to provide your mobile number. And every Google Account gets to deploy 10 applications with a Google App Engine admin account.
Now, To sign up for Google APP engine. Go to: https://appengine.google.com/ and if you have a Google Apps account go to: https://appengine.google.com/a/<DOMAIN.COM>
Now, sign in with your Google account and you would be asked to verify your account:
FAQ for this process is here: http://code.google.com/appengine/kb/sms.html
Now, once you successfully verify your account, you would see something like:
And click on create application and fill in the following details. For now, fill in the App ID and the App Title. Leave other options as default for now. And yes, please check the availability of your app id and this will also be your URL. The URL will take the form.appspot.com
Scroll down and you will find a “create application”. please click on it. You will also see a message: “Application registered successfully”. Now, let’s do some coding!
4. Let’s write the Hello World Python app!
create a directory and name it anything you like. I named it “parasdoshipyapp”. But remember the location of the directory – you need it later.
create a helloworld.py file inside the directory you just created. (you can edit it via notepad or pythonwin). And here is the demo code:
print ‘Content-Type: text/plain’
print ‘Hello, world!’
Now, you will need to create app.yaml file. Here is the demo code:
– url: /.*
In the first line, you add the app id (remember, we had created an application id in step 3)
And the last line is the file that has the code. In this case, the code is meant to print just couple of lines.
5. Test and upload on Google App Engine via Google App engine Launcher.
open Google App Engine Launcher:
Go to File –> create new application, and you will see:
Add the app id in the application name and the directory of your app. In my case, it is “parasdoshipyapp” and click on create.
Now let’s test it locally.
Click on “Run” to test it locally. Note the port no. In my case it is 8080 so I am going to go and open “http://localhost:8080/” on my browser:
It runs and so let’s deploy it on cloud (Google App Engine)
click on “deploy” and enter your Google Account credentials. Note the projects field is your “App ID”
Now we you will see the progress of the deploy. Let it do it’s processing and when it has successfully deployed your app, go to the URL and check out your site! Also explore the application dashboard.
And here is a hello world app I deployed! URL: http://parasdoshipyapp.appspot.com/
So that’s about it. I played with Google app engine as a part of an assignment for my UW cloud computing certificate program and I thought about documenting the process so may be it can help someone. Also refer to Google App Engine Getting started documentation here: http://code.google.com/appengine/docs/whatisgoogleappengine.html
If you are searching for a tutorial to help you get started with Java on Google App Engine. Here’s the tutorial: Getting started with creating Java app on Google App engine – Guest Post by Dhwaneet Bhatt
In earlier blog post, we talked about how to upload excel file to SQL Azure via the Data transfer tool found in SQL Azure labs. In this blog post, we will see how to upload an excel file to windows azure blob via this tool codenamed Data Transfer. So let’s get started.
1. Go to https://web.datatransfer.azure.com and select the second option – Windows Azure Blob:
2. Provide the credentials of your storage account (I checked the URL, it has https) – And provide account name in the format.blob.core.windows.net , container name and if the container of that name does not exist than it would be created, and the key which you can find from the storage accounts in Azure management portal. click on next.
3. now point the tool to the file you wish to upload and click on Import.
4. So that’s it Done! you will find the files you uploaded on My Data > Blobs Tab.
And you can view the file through My Data tab. (excel file will be downloaded and viewed via excel on your machine)
And during my experiments, I also tried uploading a .txt and .xml files. It works too!
Overall, Data Transfer makes our life easier by providing a web interface to upload data to SQL Azure and Windows Azure blobs.