Dave, yes we are replacing most our copy utilitites with eseutil. it rocks

There is still one problem, sometimes...

you could try powershell scripts which are callable from TSQL also.

you may want to run sp_changedbowner 'sa' on that database.

Once you have setup profiler to do whatever you want you can script the trace definition from Profiler UI.

Then run those at will with sp_trace_xxx procedures

Jeff Moden (11/28/2007)

---

That's easy... it would be the person with the most to loose if the design is bad 😉 That's the only way someone will be interested enough...

If what you are after is to implement some sort of "rollover" file read, that logic is up to you. There is nothing built-in for that.

I would check that all databases are in compatibility mode = 90.

yes I thought the hotfix would help ... but it was just cr@p. My files are 100GB + so the OS memory cache somehow tries to "help" me when...

Totally agree SCOPE_IDENTITY() works very well.

CHECK your client code or the server for "after" the fact processing ...

Buxton69 (11/26/2007)

---

It's not the views, sp_MSforEachTable only works on tables.

I don't think it's the way that the indexes were created although that is very interesting to know, I think it's...

In addition watch out for "autoshrink"/"autoclose" options too.

Happy to help 😀

you should add UPDLOCK hint to the "select" statement on the batch...

Cheers,

Kyle Schlapkohl (11/26/2007)

---

The script is run as part of a BI package that is designed to run on over 100 databases. Also, selecting from the sys.* is not an option...

Definitely you should change the App. It is a "bad" design to do that in two separated calls.