Viewing 15 posts - 1,366 through 1,380 (of 5,103 total)
Dave I (11/26/2007)
Did you try the ESEUtil program that comes with exchange?http://blogs.technet.com/askperf/archive/2007/05/08/slow-large-file-copy-issues.aspx
Dave, yes we are replacing most our copy utilitites with eseutil. it rocks
There is still one problem, sometimes...
November 28, 2007 at 2:04 pm
you could try powershell scripts which are callable from TSQL also.
November 28, 2007 at 1:58 pm
you may want to run sp_changedbowner 'sa' on that database.
November 28, 2007 at 1:57 pm
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
November 28, 2007 at 1:55 pm
Jeff Moden (11/28/2007)
November 28, 2007 at 1:51 pm
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.
November 26, 2007 at 4:21 pm
I would check that all databases are in compatibility mode = 90.
November 26, 2007 at 4:19 pm
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...
November 26, 2007 at 4:13 pm
Totally agree SCOPE_IDENTITY() works very well.
CHECK your client code or the server for "after" the fact processing ...
November 26, 2007 at 3:24 pm
Buxton69 (11/26/2007)
I don't think it's the way that the indexes were created although that is very interesting to know, I think it's...
November 26, 2007 at 2:54 pm
In addition watch out for "autoshrink"/"autoclose" options too.
November 26, 2007 at 2:48 pm
you should add UPDLOCK hint to the "select" statement on the batch...
Cheers,
November 26, 2007 at 2:44 pm
Kyle Schlapkohl (11/26/2007)
November 26, 2007 at 2:41 pm
Definitely you should change the App. It is a "bad" design to do that in two separated calls.
November 26, 2007 at 2:39 pm
Viewing 15 posts - 1,366 through 1,380 (of 5,103 total)