Alex Rosa & SQL Server & Microsoft Azure https://docs.microsoft.com/archive/blogs/alexrosa/feed.xml DECLARE dba AS human … SET dba = family + rdbms + friends + career + day_by_day + certifications + theory + real_life_experience Wed, 17 Apr 2019 03:15:27 GMT en-US hourly 1 Azure SQL Database v12 - Object Explorer wrong version and unable to rename a database in SSMS https://docs.microsoft.com/archive/blogs/alexrosa/azure-sql-database-v12-object-explorer-wrong-version-and-unable-to-rename-a-database-in-ssms Fri, 15 May 2015 07:37:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2015/05/15/azure-sql-database-v12-object-explorer-wrong-version-and-unable-to-rename-a-database-in-ssms/ Few weeks ago I was creating a demonstration using Azure SQL Database v12 and I notice that the version shown in SSMS Object Explorer was different than it was shown through T-SQL commands, like @@version.

So, let me share with you what I found so far regarding to this situation.

 

01 Problem

SSMS Object Explorer shows Azure SQL Database version 13.0.15 or 13.0.16, but the SERVERPROPERTY(N'ResourceVersion') or @@Version commands return the version 12.0.2000.8

 

01 Cause

- Using SQL Server Management Studio (SSMS) 2014 RTM, Version 12.0.2000.8

 

01 Solution

Install the latest Cumulative Update, in this case I used CU7, and SSMS Object Explorer will show the correct Azure SQL Database version

 

 

02 Problem

If you right click over the database name to show the possible actions, you'll see that the option RENAME is not enabled and you cannot rename the database through the graphical interface

 

02 Cause

Looks like, SMSS still recognize the next Azure SQL Database version number instead of the current version, see RESOURCEVERSION result (click on the image below to maximize)

 

02 Workaround

You can use T-SQL, ALTER DATABASE, to rename the database

ALTER DATABASE demo01v12 MODIFY NAME = demo01v12_new

 

So, that's what I found so far and I'll update this post if I find anything else.

 

]]> Comparing DMVs between Azure SQL Database V11 and V12 https://docs.microsoft.com/archive/blogs/alexrosa/comparing-dmvs-between-azure-sql-database-v11-and-v12 Tue, 12 May 2015 05:52:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2015/05/12/comparing-dmvs-between-azure-sql-database-v11-and-v12/ As we know, the Azure SQL Database V12 had a huge improvement in terms of features available. Per consequence, more DMVs were enabled.

You can check it out what's new in SQL Database V12 in the following link:

https://azure.microsoft.com/en-us/documentation/articles/sql-database-v12-whats-new/

 

In V12, there are: 117 new DMVs, 28 were kept and 4 were removed.

It's important to say that some DMVs will not return rows, because the feature related to them is not enabled yet.

 

Also, I'm sharing with you one way to compare V11 with V12, see sample below and PDF attached for more details.

 

 

MSAzureSQLDB_DMV_VersionComparison.pdf

]]> Mind Map - Windows Server 2008 R2 Failover Cluster https://docs.microsoft.com/archive/blogs/alexrosa/mind-map-windows-server-2008-r2-failover-cluster Sun, 12 Apr 2015 12:25:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2015/04/12/mind-map-windows-server-2008-r2-failover-cluster/ During my studies, I use to create mind maps to help me memorize or remember key words of a topic.

In this post, I'm sharing with you one of my mind maps.

Take a look and see if you know every key word included in this mind map or if you need to research about some of them.

I hope you enjoy.

 

]]> Installing SQL Server 2008 + Windows Server 2012 = Cluster Service Verification FAILED https://docs.microsoft.com/archive/blogs/alexrosa/installing-sql-server-2008-windows-server-2012-cluster-service-verification-failed Sun, 17 Aug 2014 13:21:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2014/08/17/installing-sql-server-2008-windows-server-2012-cluster-service-verification-failed/ You can get more details and screen shoots visiting Marcelo's blog post.   Problem

During SQL Server 2008 or 2008 R2 over a Windows Server 2012 the Cluster Service Verification Failed. Cause

The MsClus.dll library is disabled by default in Windows Server 2012, and installing "Failover Cluster Automation Server" re-enable it. Solution

Install Cluster Automation Server (add-windowsfeature RSAT-Clustering-Automation Server)

Reference: https://support.microsoft.com/kb/2681562  (Known SQL Server 2008 R2 and SQL Server 2008 setup issues)   After this installation in all Cluster Nodes you can re-start SQL Server 2008 installation and the Cluster Service Verification will pass.    

]]> Extended Events - Table of events per SQL version https://docs.microsoft.com/archive/blogs/alexrosa/extended-events-table-of-events-per-sql-version Thu, 07 Aug 2014 14:49:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2014/08/07/extended-events-table-of-events-per-sql-version/ I was reviewing XEvents and I've decided to share the file attached where you can find the Extended Events per SQL version, an easy way to figure out which event is available in each version.

Count of events:

SQL 2008 = 254

SQL 2008 R2 = 264

SQL 2012 = 618

SQL 2014 = 873

 

The image below is an example.

You can download the attached HTML file with all events.

 

 

 

XE_Events_per_SQLVersion.htm

]]> Max Worker Threads - Lower and Upper Bounds - The Correct Formula https://docs.microsoft.com/archive/blogs/alexrosa/max-worker-threads-lower-and-upper-bounds-the-correct-formula Tue, 05 Aug 2014 14:52:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2014/08/05/max-worker-threads-lower-and-upper-bounds-the-correct-formula/ Last week I was discussing with some friends, how SQL Server works with threads: Max Worker Threads - Lower and Upper bounds, Thread Pooling, SQLOS Scheduling, Parallelism, Resource Governor - CPU limits, Call Stack, Thread Starvation, Dedicated/System and User Threads...so, all the topics related to Threads.


If you don't know exactly how Process and Threads works in Windows, I strongly recommend you to read Mark Russinovich's blog post: Windows Pushing the limits: Process and Threads.

Also, Denzil Ribeiro's post, is very useful to understand how Max Worker Threads works.


Lower bound

Q: Is it possible to set Max Worker Threads lower than Minimum Value?

A: No, it's not possible.

128 threads is the minimum value for this configuration, if you try to set it to a value lower than 128 the following error will be raised:

              /*------------------------

                sp_configure 'max worker threads', 127

              ------------------------*/

               Msg 15129, Level 16, State 1, Procedure sp_configure, Line 161

               '127' is not a valid value for configuration option 'max worker threads'.



Upper bound

Q: Is it possible to set Max Worker Threads higher than Formula Value (table below)?

A: Yes, it's possible.

Manually, you can set the value higher than the calculated upper bound.

If you use the Default Value, 0 (zero), the formula below will calculate the upper bound.

In Books Online we have some important references, but the formula for computers with more than 64 processors is missing:

            Configure the max worker threads Server Configuration Option

            Server Configuration Options (SQL Server - MAX WORKER THREADS)



In the table below, you can see the formula for each architecture and numbers of processors:

            


In the formula we have the numbers:

        256 and 512, these numbers are the initial maximum workers that can be created
        
        8, 16 and 32, these numbers are the additional numbers of threads per processor
 

 

]]> PerfMon - Where are the process counters? https://docs.microsoft.com/archive/blogs/alexrosa/perfmon-where-are-the-process-counters Sat, 12 Jul 2014 17:30:00 GMT https://blogs.msdn.microsoft.com/alexrosa/2014/07/12/perfmon-where-are-the-process-counters/ Almost everybody knows how to use Windows Performance Monitor, or just PerfMon, but there are some tips & tricks that many people don't know and they should know, because can have a negative impact in your data collection and analysis.

One of them is how to save the output file: Binary (BLG) or Comma Separated (CSV) ?

There are pros & cons for both of them, but if you use CSV format, be aware that you can miss important counters during the data collection.


Scenario:
High CPU usage during a period of time.

Cause:
A process started and consumed more CPU than expected.

Goal:
Identify which process was running and caused the high CPU usage.

 

So, you can use Perfmon to collect \\Process(*)\%Processor Time, this way you can identify which process was consuming the most of the CPU in a specific period.

If you use CSV format to save the output, all of the processes started after the data collection start time WILL NOT be included into the CSV file.

You can see in the image below that PROCESS06 and PROCESS07 were not included in the output file, and will not be detected during your analysis.

 

 

In the link below (YOUTUBE VIDEO), I'm showing you more details and a demonstration:

https://youtu.be/ruj6MtCgOEg

 

Take care...
Alex Rosa

]]>