Known Issues in the Management Portal for SQL Database
Updated: July 24, 2012
Use the following sections to identify known issues in the Management Portal for SQL Database and to implement corrective action.
Issue.1 – Opening or Pasting a Large Transact-SQL Script
If you open a large script file - If you open a Transact-SQL file that exceeds 250k characters in the portal, the first 250k characters will be displayed but a warning message will also be displayed: “The input is truncated because it has exceeded the maximum number of characters allowed.” In this case, the entire script will not run because only 250k characters are supported.
If you paste a large script file – If you paste a Transact-SQL file that exceeds 250k characters from the clipboard into the portal, the 250k character limit is not enforced and the entire contents of the clipboard will eventually get pasted into the Query Editor window. However, running a large script file is likely to result in poor query performance, based on the size of the script being pasted.
If you must run a script larger than 250k characters, paste the contents into the Query Editor rather than opening the file directly. When working with large scripts, be aware that you might experience reduced performance.
In either case - whether you open a Transact-SQL file or paste the contents of the file from the clipboard - colorization will be disabled if the script is larger than 100 KB. If you reduce the size of the script to less than 100 KB, colorization will be enabled again.
Issue.2 - Database Size Displayed in the Azure Portal is Different than the Database Size Displayed in the Management Portal for SQL Database
The Management Portal for SQL Database shows database size information from SELECT SUM(reserved_page_count)*8.0/1024 FROM sys.dm_db_partition_stats that does not include metadata size. The database size shown in the Azure Management Portal does include metadata size. We will provide an update in a future release to make results consistent. To get the exact billable size of your database in the Management Portal for SQL Database, open the query editor, connect to master, and run the following query: select * from sys.resource_usage where database_name = 'test'.