No issues. The Win 7 clients can connect to a SQL 2000 db. The clients are backwards compatible. It's the server code that's the issue in trying to install that...

Excellent comments, and thanks for the debate.

replication would do this.

If you have some type of date or timestamp field that can determine what's "new", you can build an SSIS package to easily move these.

AFAIK, the resource governer doesn't understand anything about the other instances.

It's a limiting factor, not a governing factor. If you have two groups, each allowed 70% max CPU, separate instances,...

Are you an administrator on your machine?

What edition of SQL Server 2005 are you installing?

Are you running SQL 2000 on the XP clients? Or do they connect to a server?

If you are installing SQL Server 2000 on the client, as MSDE, no, AFAIK, you...

Are you sure your function is returning one for the SQL Server Agent service account (or proxy account)?

If you remove that function call, does it work?

CAST and CONVERT http://msdn.microsoft.com/en-us/library/ms187928%28SQL.90%29.aspx

Wow

You would change the connection string for each platform, and would need drivers to connect to each server.

Note that each of these products uses a different version of SQL, so...

Actually, I think in OODBMS or HDBMS, we'd get worse design. Harder to understand. My point is that RDBMS is the easiest (relative) of the 3. Not sure where column...

yes, clustered index = data. No separation there, so it's the largest size.

I think that if you move from datetime to smalldatetime, you will make the indexes smaller, both NCs...

If that's the case, I'd suggest they keep two sessions on their workstation, one with a higher privilege account. Handle issues administratively. Don't allow Outlook, etc. in the high privilege...

Tx, updated with CU6 for SP3 and CU16 for SP2

I think part of the reason that relational dbs, and not object or hierarchial or column dbs rule is the they have a low barrier to entry and they are...