Like most SQL Server service packs, the latest service pack by Microsoft for SQL Server 2000 is simple to install. Don't let this deceive you though. A step mishap can leave your system in an inconsistent state and cause major problems when users begin to hit it again. This article will provide you a step-by-step guide to installing Service Pack 1 for SQL Server 2000.
2001-06-18
5,421 reads
2001-06-15
7,459 reads
In this article by Brian Knight, he explores how to install Service Pack 1 for SQL Server 2000 and some of the catches. This service pack is one of the largest in SQL Server history. Learn what was fixed here.
2001-06-13
8,273 reads
Anyone that has ever forgotten a WHERE clause in an UPDATE or DELETE syntax still has the bruises. Log Explorer 2.0 has a way of reversing your mistakes by peering into the transaction log and rolling back transactions. This, week Brian Knight reviews this product.
2001-06-11
7,751 reads
XP_FILEEXIST gives you the ability to find files and directories. Find out how else you can use it in this article.
2001-06-08
20,633 reads
When trying to implement data from an external source, very rarely do you receive the data in perfect condition. In part one of this series, we show you how to clean your data using DTS.
2001-06-01
8,417 reads
Sp_MSforeachdb gives a DBA the ability to cycle through every database in your catalog. Find out how to use it.
2001-05-31
13,787 reads
By default, all NT administrators of the domain that your SQL Server is installed in, have SA rights in every database. This presents interesting challenge for DBAs, political and technical. Does your NT administrator group need SA rights to every database? The answer is no.
2001-05-25
4,074 reads
In some cases, you may have to be able to quickly disable all the constraints and triggers in a database. This article shows you how to do this with a few lines of T-SQL.
2001-05-24
10,052 reads
This article will show you how to use the FileSystemObject to determine the existence of a file inside DTS.
2001-05-23
8,355 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