SQL 2000 forced fixed memory usage with AWE enabled, but SQL 2005 does not.

Here is a pretty good article explaining in detail:

http://blogs.mssqltips.com/blogs/chadboyd/archive/2007/10/15/sql-2005-dynamic-memory-managment-with-awe-enabled.aspx

There are a couple of important things to note.

AWE...

It would help if you posted the remainder of what you are trying to do.

Right now, you have a USE statement with no commands after it.

I assume there is more...

You cannot use "USE" with a variable.

You also don't need to create a cursor - there is a system procesure to help you.

Try something like this:

EXEC sp_MSforeachdb @Command1 = '

USE...

You have to create the temp table first and then insert into it.

You can do this if you put your check constraint into a UDF. Pass in a show and a season number and return a boolean and then use the...

Yes, you can do both.

Replication from 2000 to 2005 works fine, but it can be a bit trickier to set up. I have found it easiest to configure the...

Where is the source, destination, and VS development machine on the network?

Remember, when you run a package from the SQL Agent, it runs locally on that SQL server (which may...

It is best to install them in the correct order. Trying to install the SQL 2005 tools after installing VS 2008 is a bit tricky. There are also...

Make sure you put the field into a table that will not have any schema changes - the plan sounds good to me.

If you make that work, it would make...

I agree.

This is one of the features that feels like it does nothing but help facilitate having a poorly designed application. It's like not having foreign keys because you...

Not really, SSIS is very sensitive to schema changes because components store schema in inputs and outputs.

If you can identify the access database version somehow, you could store multiple versions...

The insert and update conflicts are probably just bad SQL somewhere. Make sure your processes do not lock the same records.

That's not true, cascaded deletes are logged.

I assume you mean using the cascading delete vs. using some combination of triggers to automatically delete child records associated with a parent record.

I would use the built-in tools if...

I am not sure exactly what you are saying regarding some packages getting a NULL, but if you have 10 packages all updating the same table, they may conflict with...