I'm not sure I follow you completely.

It sounds like you have two instances of SQL Server on one computer. You are trying to upgrade one of the instances to...

I'd start by finding out what queries are slow, then find out why. More often than not, that's the problem. Run a trace if you don't know which...

Look up "Dynamic Management Views and Functions" in Books Online, you'll find what SQL 2005 has for that kind of thing.

For example, sys.dm_exec_connections, will give you data about the connections...

You're definitely on the right path.

One thing you might want to look in to is DDL triggers. They can track a lot of the change scripts, etc., and you...

Does the table you're querying have an ID column or some other primary key?

If so, a union statement might be better than dynamic SQL for this.

To simulate multiple users, I scheduled 10 jobs which ran the proc 1000 times each, all running at the same time. Run time averaged 46 milliseconds for each job....

By going one step further, and setting the proc to take an XML input parameter:

create proc [dbo].[ParamsTest4]

(@DateList_in XML)

as

set nocount on;

declare @Date datetime;

;with Dates (DateIn) as

(select result.value('(i/@date)[1]','datetime')

from

(select t.c.query('.') as Result

from...

I finally got a chance to run a speed test on a proc that does it's own string-split, without calling a UDF.

Same test as before:

create proc [dbo].[ParamsTest3]

(@DateList_in varchar(max))

as

set nocount on;

declare...

What I've had to do is create the backup on a local drive, then copy it to the network as a separate action.

If running them in VS works for you, there's no reason not to do it.

Assuming both databases are on the same server, but with different names, and the table has the same name in both copies, it will look something like this:

update table

set column...

Yes. All other things being equal, the join version is immensely faster. The only time you might want to break it up (and you still wouldn't use a...

The idea of a many-to-many table is that you have one ID for the row in one table, one ID for the row in another table, and a many-to-many table...

Generally, on a logging table, I don't create any indexes, constraints, defaults, etc. The whole idea is to make inserts into it as fast and efficient as possible. ...

http://www.zip-codes.com

They issue monthly updates. It's $39.95 for a year of updates for the US. Multiple file formats available and all that.