Documented and Undocumented Trace Flags for SQL Server 2000 and 7.0
This article contains descriptions of 65 documented and undocumented trace flags currently available in SQL Server 7.0 and 2000.
2002-07-24
14,910 reads
This article contains descriptions of 65 documented and undocumented trace flags currently available in SQL Server 7.0 and 2000.
2002-07-24
14,910 reads
In this article by Randy Dyess he shares with you the script on how he audits his environment and outputs reports of the permissions that users have.
2002-05-30
9,912 reads
As you advance in your skills as a Transact-SQL developer or SQL Server database administrator there will come a time when you need to override SQL Server's locking scheme and force a particular range of locks on a table. This article by Randy Dyess shows you how to optimize your queries using table hints.
2002-04-15
21,938 reads
Ever been placed into a new environment and couldn't
find an ounce of documentation? This article is the first in a series that will help you make an audit of your new environment
and determine if any SQL Server login does not have a password, has a password the same as the login name or a password that is only one character long.
2002-04-02
10,441 reads
One of the most overlooked areas in optimizing SQL Server and Transact-SQL is the recompilations of stored procedures. A database getting thousands of recompiles an hour will suffer in performance and show short term blocking that will affect the database users. This article by Randy Dyess shows you some of the ways you can avoid stored procedure recompiles.
2002-02-26
25,035 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers