In this post, I am sharing the best method for generating the DROP script for different SQL Server objects like Table, Function, Stored Procedure.

A Database Developer may need DROP script for different purposes, and I found different T-SQL scripts which we can use for generating the DROP Script.

But while dropping, we should not forget about the object dependency. In which sequence, we are putting objects in drop script that is very much important.

We can do using scripts as well, but I would suggest “SSMS Generate Script Option” which automatically checks the dependency and put the objects in proper sequence.

Using this option, you can select the type of object with their properties like indexes, constraints.

I shared many SQL DBA/Developer scripts, but in some cases, we should go with the TOOL.

Use SSMS Generate Script Option for generating the DROP Script for objects:

Step 1: Open SSMS
Step 2: Right-click on Database and go to Task -> Generate Scripts…
Step 3: Select type of object or select all objects
Step 4: Select advance option and Select “Script DROP” option
Step 5: Included/Remove necessary child objects like Indexes, Constraints
Step 6: Finish

SQL Server uses a Maximum Degree of Parallelism (MAXDOP) for achieving the parallel query processing to increase the query execution performance.

The default setting of MAXDOP is 0 means your query execution plan chooses the maximum degree of parallelism automatically.

Which is OK, but in big transaction system you should limit your query by specifying an explicit value of MAXDOP (Number of CPU Core for Parallel Query Execution). Which requires proper analysis of your system loads, CPU configuration and number of concurrent connections.

Below are some different ways to change the value MAXDOP.

Using SSMS:

In SSMS, right click on server go to Server Properties -> Advanced -> Parallelism -> Max Degree of Parallelism. Default is 0.

Using sp_configure:

sp_configure 'show advanced options', 1;
GO
RECONFIGURE WITH OVERRIDE;
GO
sp_configure 'max degree of parallelism', 8;
GO
RECONFIGURE WITH OVERRIDE;
GO

Using MAXDOP hint option at query level:

SELECT *
FROM [Person].[Address]
OPTION (MAXDOP 1)

In this post, I am sharing a SSMS Client Statistics Screen Shot to get more details than STATISTICS IO of SQL Server.

While troubleshooting the performance of a query, we enable the STATISTICS IO to check the number of data like total logical reads, total physical reads. The basis of this result, we are taking few decisions for tuning our SQL queries.

But, What if you want to know more statistics of your queries.
What is the other option to get more statistical information of query?

The Option is Client Statistics which you can enable in SSMS by pressing a key (Shift + Alt + S) or find Client Statistics button next to Actual Execution Plan button.

Once you enable Client Statistics, you can get main three types of more statistics like Query Profile Statistics, Network Statistics, Time Statistics.

Execute below sample code and check your Client Statistics in SSMS:

CREATE TABLE tbl_ids (ID INTEGER)
GO

DECLARE @id INT;
SET @id=1;
WHILE @id < 10000
BEGIN 
    INSERT tbl_ids 
    VALUES(@ID) 
    SET @id = @id + 1;
END

In SQL Server Management Studio 2016, DBA can close all the T-SQL query windows without saving them because It has a new feature like enable/disable unsaved query prompt while closing the query windows.

It is mostly helpful to SQL DBA because they are opening lots of query windows for their testing purpose and which are not that much important so that they can close SSMS without disturbing by any prompts.

But change this option with caution, because it closes all your unsaved query windows.

You can change this option in SSMS -> Tools -> Options -> Query Execution.

SQL Server 2016 has a fixed of SSMS crashed error on Edit 200 Rows for Views. Previously, when you were trying to Edit 200 Rows for Views, SSMS was crashing.

With the new SQL Server Management Studio, it is not crashing now. But you cannot update all types of views; you can Edit 200 Rows for those views which are updatable.

If you are trying to update view which is not updatable, you will get a below error message window, but SSMS is not crashing now which is a good thing.

In this post, I am sharing one option to hide all system objects in Object Explorer of SQL Server Management Studio.

If we do not require, we should not load unnecessary system object in object explorer of SSMS.

We can hide this system objects from the menu,
Tools -> Options -> Environment -> Startup -> Check Hide System objects in Object Explorer.

After this check, close SSMS and open again for this effect.