I have written a blog post on beyondrelational site about a SQL Azure DMV – sys.dm_db_partition_stats that can be used to extract information about database size and size of each individual database object. To read the article please go to: http://beyondrelational.com/blogs/parasdoshi/archive/2011/05/30/sys-dm-db-partition-stats-a-sql-azure-dynamic-management-view-dmv-to-calculate-database-size.aspx
Go to http://beyondrelational.com/whatisnew/sqlserver/azure/default.aspx to explore the features being added with each release of SQL Azure. You will be interested to know that unlike other products, the release cycles of SQL Azure is rapid and in a year you can expect 4-6 service updates (releases). On http://beyondrelational.com/whatisnew/sqlserver/azure/default.aspx , you will find the information about past releases organized in a list format and also information about latest releases of SQL Azure.
I would like to thank Jacob sir for his encouragement and support! Thanks sir!
I have written a step by step guide on how to install Adventure works LT DB, a sample database available on codeplex, at my beyondrelational site. here is the link to the article: http://beyondrelational.com/blogs/parasdoshi/archive/2011/05/27/let-s-install-an-adventure-works-lt-database-on-sql-azure.aspx
I have written a blogpsot on my beyondrelational site about how to configure SQL Azure firewall from Azure management portal. Have a look at the article – click here
As of now, SQL Azure only supports one account administrator and one service administrator. So if there is a need to have a need for more people to manage the SQL Azure service, then go and vote for the feature ‘ability to have more than one account administrator and/or service administrator’ @ http://uservoice.com/a/kcZVd
Also you may want to read a related blogpost on MSDN blog: “Co administrator doesn’t see SQL Azure in Portal”
Earlier, i had logged in the idea “multiple servers (located in different data center) under single subscription” @http://uservoice.com/a/amp50 which got completed and it shows that team is actively monitroing this forum – so if you have any idea on SQL Azure, go and share your idea on mygreatsqlazureidea.com
I have a written a step by step guide on how to import data from SQL Azure to PowerPivot. In the article, i have also discussed couple of considerations while entering the SQL Azure credentials using the ‘SQL server native client 10.0’.
you can read the guide here:
In this blog post, i will tell you why you should not use following query structure with SQL Azure:
select * from [tablename]
1) ‘ * ‘ is bad for performance. This is the fact that is pointed out in most of the performance tuning learning series. It is a good practice to retrieve only the columns that are required.
Apart from this – there is one more reason.
2) If you look at the contemporary pricing model of SQL Azure, you will notice that with SQL Azure, we are charged with the data transfer that takes place with the SQL Azure database. The cost is directly proportional to the amount of data that is transferred in and out of the data center. Note that if we have our app on Azure platform and it is hosted in the same data center as that of our SQL Azure database, then no cost will be applied but in other scenario’s, data transfer cost apply.
So, if you retrieve column that is not used then you will be unnecessarily wasting money. Thus avoid using ‘select * ‘ wherever possible!