That was a good catch. Looks like I need to write a good one pager on this and include all information

Thanks for the update. Good to have the answer listed here for others.

The "let me google that for you"

You choose where you install each version. The named instance of 2005 will have nothing to do with the 2000 instance you have installed. If you upgrade, it will keep...

Wayne,

Hadn't seen that before, but it's great. I bookmarked it to use it for some question.

Yeah, those dates from Jason sound right. We upgraded from 4.2 to 6.0 to start a dev project, and then about 6 months in 6.5 came out. I don't remember...

Couple things I've done.

1. Back up locally. SQL Server does not tolerate network delays and it's not worth having a backup fail.

2. Do not use the same set of disks...

I almost shudder to post this, but you all might like this:

http://lmgtfy.com/

as a sample, let me Google clustered index for you: http://lmgtfy.com/?q=clustered+index

#1 - You restore Sun full, Thur Diff (00:00 Thur) and logs from 00:00 Thur to failure.

#2 - You restore Sun full, Wed diff, all logs you have after that.

What do you know. I'm surprised it was there back then. Wonder if it was in 60

I think you'll need NT 4 for this. It installed in W2K, but there were warnings, might be issues.

Where's the reference for it? I don't think it existed.

PK != clustered, and they don't have anything to do with each other. It's like saying a tall, red building. Tall and red don't necessarily relate in any way.

PK -...

You cannot give users access in SQL Server and force them to only use your application. That's not how SQL Server works.

So if you want to limit them to just...

sp_who2 didn't exist in SQL 6.5

😉

It was sp_who. When they went to 7 or 2000, they kept sp_who and added sp_who2

I think the only way to do this is David's suggestion, which is essentially a data warehouse. Move the data over periodically, every hour or so, and build reports off...