New answers tagged sql-azure
Kendra here (the author of sp_BlitzIndex) First, thanks for being interested in the procedure and trying it out. Azure doesn't expose all the dynamic management views that we get in the boxed product. I do actually reference sys.dm_db_partition_stats, but there's other info I need to get from sys.partitions for other users. (Is it using compression? What ...
I got a response through their help email. The full text is below: Hi! sp_blitz doesn't work in Azure. The value of Azure is letting someone else be your DBA. ;-) I guess the answer to my question is be bold or find another tool... NOTE: They mentioned "sp_blitz" instead of "sp_blitzindex" in their email response. That might be a simple typo, but I ...
In your particular case it doesn't really matter since both your unique clustered index and your primary key are on the same column(s) but there are two minor differences between the two. A primary key requires that all columns be non-nullable. A unique key allows NULL values. You can have only one primary key. You can have multiple unique keys. Either ...
It doesn't need a separate index. It's only done that way because you've actually told it to be in the script. You could do this with the same functionality: CREATE TABLE [dbo].[JobItems] ( [ItemId] UNIQUEIDENTIFIER NOT NULL, -- lots of other columns CONSTRAINT [JobItemsIndex] PRIMARY KEY CLUSTERED ([ItemId] ASC) );
I can reproduce the plan that you describe on SQL Server 2012 (on prem) by running the DDL in your question and then fiddling the stats so SQL Server thinks that the table is much larger than reality. UPDATE STATISTICS [dbo].[JobItems] WITH ROWCOUNT = 10000000, pagecount = 10000000 And then running the query with OPTION (MAXDOP 1, CONCAT UNION, ORDER ...
You would need to specify if you are referring to Azure SQL Database (PaaS) or SQL Server on an Azure VM (IaaS). As already noted TDE with Azure SQL Database is only available with V12 which is only available in certain regions. If you an Azure VM is what you are working with you can implement TDE in SQL Server after the VM is built, even after SQL Server ...
So this may be an old question, but the problem is still relevant today. The only way that you can alter the administrator of an Azure Sql Server, is to create a new SQL Server. Once the administrator has been set, you can reset their password, but not the name. I just ran into this same issue and had the same #facepalm moment.
We found that with contained databases / contained users you must specify: GRANT CONNECT TO [YOUR_USER] Otherwise CONNECT seems to be revoked by default. Once we made the above change, we could access the database.
There is now a "light version" available, where you can analyze your queries and see resource consumption. http://blogs.msdn.com/b/benko/archive/2012/05/19/cloudtip-14-how-do-i-get-sql-profiler-info-from-sql-azure.aspx
Top 50 recent answers are included