SQL Agent can be used to create the schedule. As posted above, you just need to run a script to start a trace. I recommend output to a file.

You can join anything on anything through a TSQL statement. No requirements at all. You might get some... interesting... results, but there are no strict requirements.

However, if you're talking about...

I wouldn't even call it apples & grapefruit. I'd say it's apples & chairs that you're comparing. Good luck sitting on the former or eating the latter. MVP can be...

Scotch... and beer. Or beer... and scotch.

Single malt (Highland or Orkney) followed by a good ESB... ah, makes life worth living.

I just tried QA against 2008. It works. Nominally. I haven't run a full-on regression test or anything.

I'm sorry too. I thought you, the OP, were trying to find ways...

OK? What's the problem and/or question?

You've got a cursor. It looks like it's doing updates.

It's hard to comment in any other way without knowing what you're trying to do...

"free admission to the contest"

I'm pretty sure the contest is free.

No, I don't need to see the "best minds" speak. I sat through a session with someone that I really...

First, don't run the profiler gui on your production systems. Instead use profiler to create a server-side trace (do a search on that phrase, it'll tell you everything you need...

There are several white papers on optimizing tempdb available...

I don't understand what ISQLW does that SQLCMD does not?

From the sounds of it, you really might benefit from Powershell.

Gail is 100% correct.

You could look into using snapshot isolation as a way to reduce locking issues. It increases the load on tempdb and some on the CPU, but...

Import/Export uses SSIS. You can go to SSIS directly. It's more work, but you can make a more efficient DTL.

In a perfect world, no. In reality, yeah. But specifically what would be the difference? I'm not sure. I haven't found the export wizard to create the most efficient ETL...

There is a template, but, like Gus says, unless they do precisely the same thing every time to create a new proc and no one ever just starts typing (same...

Assuming the source tables are not being updated, no, it should only be putting shared locks on them for reading. It might cause excessive I/O, memory, or CPU use while...