Nevermind:

sp_configure 'default trace enabled', 0

go

reconfigure

go

In my sitituation, at least in DEV and QA, the preponderance of "disasters" involve an errant query. In this case, I restore to a new database and copy the...

Is there any way to turn this trace off?

Couldn't you effectively do this by putting data and indexes on separate filegroups and only restore the data filegroup? Then just drop/recreate indexes?

Baseline is the same as a benchmark.

That's what establishing baselines is all about. This tool can help you do that, but no tool does it for you.

I don't think you'd want to use this facility for point in time monitoring. However, you could use the data to establish benchmarks. And, as we do, use...

This actually happened to me...twice! Both times I reported it; either to my supervisor or the payroll department.

If it's the same error I've encountered in the past, it's because the step command (enclosed in single quotes ') spans multiple lines in the script.

What I usually...

Based on the rest of Microsoft's documentation, I'd choose the former. :crying:

I cannot speak for Microsoft, but my guess would be they eliminated superfluous constructs from the physical model in the interest of performance.

I do the same thing. ...

My 2 cents:

Logically, every table should have a primary key. Once we move into the physical realm, my philosophy is "less is better" or "prove you need it". ...

I started working on it this morning. I should have something available no later than mid-week.

That makes sense. I've run into that myself before.

Perhaps that restriction pertains to a #TEMP table? All I know is the DTS works as coded.