2007-08-01
1,671 reads
2007-08-01
1,671 reads
Most SQL Server DBAs will never need to read the registry for their instances, however in case you do find yourself needing to read or write something in SQL Server 2005, Vince Iacoboni brings us a technique for performing both of these actions.
2007-07-31
8,873 reads
2007-07-25
2,050 reads
2007-07-17
1,787 reads
2007-07-16
1,499 reads
2007-07-12
1,811 reads
It's been almost three years since SQL Server 2005 was released and Steve Jones current recommendation is that you don't upgrade right now. Read on to see why he's giving this advice.
2007-07-11
23,698 reads
When your database transaction log is out of control, there is only one man who can tame it.
2007-07-06
2,611 reads
2007-07-05
1,862 reads
With the introduction of SQL Server 2005, Microsoft now allows you to write Data Definition Language (DDL) triggers to perform actions when events occur on your server. In this article, Greg Larsen discusses (examples included) some of the things that DDL triggers can be use for.
2007-07-04
2,503 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