K. Brian Kelley (8/10/2009)

---

As indicated, it's really no different than multiple instances of the same version of SQL Server on a cluster. You still have to make the appropriate plans...

Well, there's the real problem with striping backups across the network. If one fails, the whole thing is no good anyways.

If this was my system I would be taking...

You are going to have to tell us what problem you are actually having with backing up across the network. How have you determined that backing up 10-15GB is...

I am not real sure I understand your problem - or in fact, what your question really is. I can, however, tell you that I currently backup a 450GB...

Yes, it is possible - and you have basically the same issues that you would with multiple instances on a single machine. Namely, you need to make sure you...

I just took a quick glance at your reports. You have a high percentage of parallelism waits - in fact, that is the highest waits you have on this...

To run an SSIS package - you have to have Integration Services installed. Doesn't matter about BIDS or SQL Server, but you do need to have Integration Services -...

What are the actual date/times of the files - what time did the task start?

Warren Peace (8/7/2009)

---

Richard, thanks for the vlidation. I know this has always been cunfusing, that's why I raised the question of it.

lol, why the hell does MS leave in...

Warren Peace (8/6/2009)

---

Carve out in SQL to start at 12GB and max out at 14GB. Then set your locked pages policy to the account SQL is running under. Make sure...

Because you installed x64 - all you really need to do is set the max memory for SQL Server. Since you installed the standard edition, you probably should not...

Is it the data file or the log file that is growing? If you find that the log file is growing - you need to identify the process that...

Right-click on the maintenance plan under the maintenance folder and select View History. That will show you how long each task takes.

Now, if you are executing the task for...

That error message is stating that it could not open the backup file, not the database file. That can be caused be several things, for example it could be...

Yes, there are quite a few known issues that you could run into. I would recommend running the Upgrade Advisor on your 2000 database before attempting to upgrade.