excellent. Thanks.

Back to my question, what is a good way to capture TempDB contention information?

What is a good way to capture TempDB contention?

I am thinking that on the create temp table(s) there is locking of syscolumns, causing contention.

How does one measure/capture this?

Timeouts in tempdb.

Deadlocks in user db.

User db uses alot of temp tables.

check that. The alias works.

Just had to configure it like below, where ServerA_Linked is the alias name.

EXEC sp_addlinkedserver

@server='ServerA_Linked',

@srvproduct='', ...

neither one works.

Microsoft told me not to use the /3GB switch in an 6GB or even a 8GB box. When AWE is enabled also.

- Not totally sure why yet. Still waiting on...

So based on this, Virtual address space is different from Virtual memory.

Virtual Address space is the total amount of addressable memory. (Physical + page file)

Base Memory - up to 4GB.

/3GB...

"The /3GB switch is used to tell SQL Server to take advantage of 3GB out of the base 4GB of RAM that Windows 2000 supports natively. If you don't specify...

So Antares686,

what does the /3GB do?

what switches do you suggest for 8GB RAM?

How about this:

GRANT

- WITH GRANT OPTION

Specifies that the security_account is given the ability to grant the 'specified' object permission to the other security accounts.

Ya I am well aware of encryption.

My point is, having the file opened with notepad is one thing, but being able to view actual data is a completely different thing....

does anyone else consider this a risk?

shouldn't .MDF's only be allowed to be opened by SQL Server?

thats not what I meant.

I am concerned about it being able to opened in notepad and data being visable.

Seems like a risk.

ok now I understand what you were saying.

you were talking about moving the "good" master.

makes sense, but not a needed step for this recovery scenario.

ok.

Based on my disaster scenario, I have the "good" system databases and all the user databases available. These are copied to another drive.

So,

1. Re-install to any location.

2. Stop Server

3. Move...