No, they don't have to be the same. Usually they are, but with a little work you can handle this. Not sure you should though. One of the nice things...

Either will work. Have you looked at the jobs collection and the job object yet?

Andy

I don't have a solution. Are you running sp1 for SQL2K? Connecting using named pipe or TCPIP?

Andy

Transactional replication?

Andy

You can use dbcc shrinkfile to reclaim the 'reserved' space, to some extent anyway. Have to be member of sysadmins or dbo to do it though. You definitely need to...

Would be interesting to do both approaches, since how they compare. Depending on how efficent DMO is, it might be faster to use procs.

Andy

Gotcha. Thanks for the follow up.

Andy

Adding jobs can be a fair sized headache. Well, adding the job is not bad, but getting the schedule done takes some work. If you're not going to be adding...

Thanks for posting Michael. Just because Im curious, why do you not want the primary key script inline? Also - using numbers instead of the constants really makes for hard...

Dan, there are certainly some interesting things you can do with object ownership. Now whether you should...thats the question! If you're using it intentionally to solve a business need, good...

Not that I know of.

Andy

I'd vote for replication, mostly because I use it a lot. The problem I've seen with log shipping is that the db stays in standby mode. Similar question was in...

I agree about reboots - not an issue when you build your own...or as much of an issue anyway. I get a lot of use/reuse out of code in COM...

No.

Try running sp_recompile 'procedure name' - sounds like maybe the query plan is bad.

Andy