For MS SQL 2000 I see at lest two ways of doing that:

1 - Put those tables on READ-ONLY filegroup;

2 - Put that login indo db_denydatawriter fixed database role;

Check BOL...

You could try this (of course, some limitations apply):

Create table dates( date datetime)

insert into dates values('2005-01-01')

insert into dates...

Karen,

If your new server is Windows 2003 this article might help you

http://support.microsoft.com/default.aspx?scid=kb;en-us;827452.

But it does not anything about 3GB file size limit.

Igor

As workaround and only as workaround you can analyze program_name column in sysprocesses table.

Run

select program_name

from sysprocesses

where spid = @@spID

You could check it in your triggers and if program_name =...

Thanks for the update, Aaron.

It's useful to know about another undocumented trace flag.

Igor

Thanks for the update, Aaron.

It's useful to know about another undocumented trace flag.

Igor

Applying the log will not simulate the load, but you can create a trace file

using SQL Profiler and then replay it in test.

Igor

Or you could try this:

Create Procedure RecCount (@Table sysname ) As

SELECT si.rowcnt

FROM sysindexes si

INNER JOIN sysobjects so on si.id=so.id AND si.indid IN (1,0)

WHERE so.name = @Table

Igor

If you are using SQL 2K and performance is not an issue,

you can do this:

SELECT *, SortColumn = Cast(b as sql_variant)

FROM   Table1

ORDER BY SortColumn

Igor

Do you have 'Auto Shrink' option enabled by any chance?

Can you restore (on the test server) your 14.7 GB backup and tell size of data and log files.

Igor

How about DBCC OPENTRAN ?

Check "Long-Running Transactions" topic in BOL.

Igor

Well, when Microsoft recommends something - you better stick with it.

What is recovery model for your database?

Does your application do any bulk-logged operations?