commentBlock = $("#comment_post_26073").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"it_user78867<\/a>
it_user78867<\/a>CIO<\/span><\/div>
<\/span>Vendor<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

SQL Azure is a service, and even it is pretty much the same as a SQL 2012/2014 server, you have to take in mind some considerations that can affect your application or your intentions on what use you will give to the SQL Engine. You can find links on the web that show the basic differences between SQL Server and SQL azure. The principal caveats is the way you can interact with the SQL Azure service and the SQL Transact commands that you can work with at an administrator level. You are limited on this commands and the things that you can accomplish. Also, there are some functionality (like temporary tables) or field types that do not work or exist on SQL Azure.\n
Also there is a limit on the number of transactions per second that you can realize, it is called throttling, you have to keep in mind that if you expect to do a great amount of transactions per second, SQL Azure could not be the service that you need.\n
There is also limits on the DB size that SQL Azure can handle. I think that right know this limit is set on 150GB. You can work around this limitation with DB federation, but requires some additional work on your queries side.\n
For a regular database operations and maintenance, it will fit well. It is a perfect integration for PAAS solutions.<\/p><\/div>