I prefer the "freak out and yell at people" method when a new one is discovered.

That way, people become a bit more afraid of installing software.

To include the necessary schema, XML is probably the way to go.  You could also use an SSIS Raw file which is a native file format for SSIS to import...

Considering you started with the procedure run time being significantly longer than the same code without the procedure, you should really look at the execution plans.

If the performance is different,...

I have not had to upgrade an edition on SQL2000, but I have in SQL2005 and you have to reapply sp1 after the edition upgrade for 2005.

After your upgrade, check...

I am posting about your first issue because I am having a similar issue.  For background, I have a 100gb data mart database and analysis services running (sp4 SQL 2000)...

We have had good luck with WinAce if you want to spend a little bit of money.  It seems to compress much better than WinZip.

Otherwise PowerArchiver command line is not...

I agree that it is bad practice, but I have seen a few applications do this in the past.  I think it is sometimes convenient to store some information in...

You need to look closely at the execution plans on both servers and examine the differences.  SQL takes a lot into consideration when creating n execution plan including hardware, indexes,...

Ultimately, the application should be able to resume.  If you wanted hibernation support for an application, this would be necessary as hardware such as wireless network connections will always leave...

I have been running transactional replication from a 2000 server to a 2005 server for several months now and I have had no issues.  The replication wizard in 2000 handled...

I have also used this task.  I found the instructions pretty good, what seems to be your issue?

The only major issue I had with it was the fact that if...

You could create a target spreadsheet in Excel 2007 and an ODBC DSN to it.  It seems a bit flakey though.

You can also create an XML document and give it...

Make sure your named instance is running under the same service account.  Most of my MAPI issues have related to the service account SQL is running under.

If you need them running...

We run Epicor here as well and we have noticed that there are some user actions in the application that cause most of our performance problems.  Between the frx reporting...

Also watch out for foreign keys.  Deletes have to verify a foreign key constraint is not being violated and sometimes this can take a long time.