2018-02-28 (first published: 2018-01-10)
3,097 reads
2018-02-28 (first published: 2018-01-10)
3,097 reads
2018-06-12 (first published: 2018-01-03)
1,973 reads
2018-05-30 (first published: 2018-01-03)
2,512 reads
When your application is running slowly, the reflex action is to blame the database queries. It is certainly true that some of the more extravagant delays can be fairly blamed on a missing index or unnecessary locking, but there are other potential villains in the drama, including the network and the application itself. Dan Turner points out that you could save a lot of time and money by working out for sure where the problems lie before diving into the detail.
2017-11-02
7,358 reads
A SQL Server, SQL Azure and Hekaton performance bench marking application that uses patterns.
2019-06-14 (first published: 2017-10-19)
5,000 reads
Any DBA who is trying to find the cause of an intermittent problem with a server or database dreams of being able to use a query or procedure take a snap of the relevant variables at the point when the problem occurred. Laerte takes an example of a slow-running query hogging resources to show that you can run queries when a WMI alert is fired, and save the results for later inspection, whenever it happens.
2017-09-20
4,188 reads
Erik Darling explains why your queries aren't scaling in production.
2017-09-06
5,344 reads
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
2017-08-02
8,420 reads
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
2017-07-13
7,641 reads
2017-07-10
890 reads
Quite the title, so let me set the stage first. You have an Azure...
By HeyMo0sh
In the realm of software development and content creation, the deployment pipeline serves as...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers