Wednesday, August 3, 2016
Thursday, July 28, 2016
Microsoft releases CU #1 for SQL Server 2016
Microsoft released their latest flagship database product, Microsoft SQL Server 2016 on June 1st 2016. After 2 months, now Microsoft announced the release of CU #1 which contains fixes for 146 issues across different categories of the product.
The CU1 has 146 hotfixes in 10 different categories as stated above. The highest no.of hotfixes are for the SQL Service.
You can download the CU1 by using the below link.
Cumulative Update 1 for SQL Server 2016
Cheers.
Friday, July 22, 2016
Denver SSUG Presentation About Latch Behavior
Yesterday I did a presentation about SQL Server Latch behavior at SQL Server User Group at Denver.
Hope everyone has learnt something and got some exposure to SQL Server latches which is internal to SQL Server and some time create issues. So that knowing about what they are and how they behaves is important in my opinion.
Below link contains the ppt and the demo scripts I used. The demo scripts are compatible with SQL Server 2014 or later.
Cheers!
Monday, March 7, 2016
How do I get access to SQL Server instance when no other access is possible
Recently I had a situation where no one knows any level of credentials to SQL a Server instance. The instance I tried was a SQL Server 2008. By default SQL Server 2008 does not provide admin access to built in Windows local admin group.
I was able to get access to it by following below steps;
- Stop SQL Server service using SQL Server configuration Manager.
- Right click on SQL Server service and get properties.
- In Log On tab, use This account option to provide a windows domain account credentials which you already know. I my case I provided my credentials for the specific domain.
- Use Advanced tab to add “-m;” startup parameter to the beginning of the parameter list. The –m startup parameter is use to start SQL Server service in single user mode.
- Click on Apply and then Ok.
- Start SQL Server service.
- Open CMD shell in administrator mode and type the following sqlcmd statement; This will test the access to the server and if it successful, it returns the SQL Server name. This is just a verification.
- sqlcmd -E -S <server name> -q "select @@servername"
- Use the below sqlcmd statement to create a new user called “recovery”.
- CREATE LOGIN recovery WITH PASSWORD = '1qaz2wsx@'
- Use the below sqlcmd statement to grant admin privilege to the user we just created.
- SP_ADDSRVROLEMEMBER 'recovery',SYSADMIN
- Stop the SQL Server service using Configuration Manager.
- Get SQL Server service properties and remove the startup parameter “-m” and click Ok.
- Start the SQL Server service.
- Open SSMS and try to connect to the server using the user name and password we created in above steps.
Hope this helps. Cheers!
Reference:
Friday, February 5, 2016
Another process has taken SQL Server assigned port
The SQL Server (MSSQLSERVER) service terminated with service-specific error An attempt was made to access a socket in a way forbidden by its access permissions..
After few troubleshooting I found this was due to the port xxxxx was taken control by another process. Apparently the process was Cluster Manager. :) So I closed the Cluster Manager and re-opened and then failover was successful. This seems to be very rare occurrence but it is possible.
Refer the below link for more details;
Server TCP provider failed to listen on...
Wednesday, September 30, 2015
Thursday, June 25, 2015
Essential Tips for Virtualizing SQL Server
Very good article on Vitalizing SQL Server. Read Essential Tips for Virtualizing SQL Server
How to interpret Disk Latency
I was analyzing IO stats in one of our SQL Servers and noticed that IO latency (Read / Write) are very high. As a rule of thumb, we know tha...
-
Do you know there is a new T-SQL command in SQL Server 2008 which facilitates you to insert several rows in single INSERT statement? This is...
-
I wanted build an expression to make a folder name dynamically. (Basically expressions are anyway dynamic in nature) So I simply used the ...
-
This can happen due to many factors like lack of indexes, out of dates statistics, if it returns a large number of records, etc. I observed...
