It sounds like you just have too many FK's against your company table. At this point, the FK relationship should be maintained via code, and not via the internal...

Have not yet done any setup with Windows Server 2008.

We do have SQL 2005 x64 on WS2003 x64. Works great.

1) NO replication - it is not for disaster recovery / business continuity

2) Agree - first look at mirroring as part of the process. Hardware failure and other localized...

I do not have the reference, but I do recall one one of the MS pages outlining that the backup file data, including the log information, had the same format,...

Both approaches are viable, and under different circumstances could be considered the best approach.

If for example, you use a domain account for the login, the user login and pw are...

The master database holds information that is specific to the local machine, and so trying to do a full master restore might not be a good idea.

As for the logins,...

Another option would be to have the top level procedure call a function rather than a procedure. Functions can return not just single values, but also tables.

In the...

Nice to know. I can see this as useful if you are building a proc that creates dynamically generated SQL. But dynamically generated code should be avoided if...

Nice academic approach. No doubt I'll have to look this over a few times for it all to sink in.

Normally I would agree, the optimizer tends to find the best path. But for this project we are running SQL2005 Standard Edition. As documented, with the exception of...

I found the answer, but from what I can tell, it is a true bug.

Below is the proc code below. The fix is to comment out the WITH...

reposting in the SQL2005 forum.

Nice job

Super. then it must be some other isseus. Thanks

Yes, it really gets down to understanding both the requirements and the tools.

I see many troubled/problem applications/systems where lack of storage knowledge was the biggest problem with the system. ...