Viewing 15 posts - 151 through 165 (of 242 total)
Out of date statistics will seriously affect the query and might mean it does lots of I/O and doesn't consider indexes.
To fix either
(1) Turn on auto create and auto update...
May 19, 2009 at 6:15 am
Out of date statistics will seriously affect the query and might mean it does lots of I/O and doesn't consider indexes.
To fix either
(1) Turn on auto create and auto update...
May 19, 2009 at 6:15 am
Normally the first option is the way to go.
If you are worried because the database grew that is what happens in normal running. You'll find it has some free space...
May 19, 2009 at 6:05 am
Thanks, I'm glad it worked so well for you.
Tim
May 19, 2009 at 5:56 am
RedGate SQL Compare will show you the differences and script them so you can bring them together again.
You can also keep a snapshot of databases so in you case you...
May 18, 2009 at 10:40 am
Tara, it is unlikely you need to worry.
If you leave SQL Server to determine how much memory it needs it will normally do this accurately. Normally it grabs as much...
May 15, 2009 at 4:31 pm
Looking at your figures reducing the fill factor on those indexes may have spectacular results.
I have a few examples of production indexes that would fragment by 50% over 24 hours...
May 14, 2009 at 6:34 am
Gail, you are never short of a decent tip, and that's an excellent one!
Passes the test of not having to write it down and almost impossible to guess or crack...
May 14, 2009 at 2:07 am
BarkingDog, this is a good question and you will probably get a number of pedantic, 'best-practice' and impractical answers to it.
For my money you tie down your production DBs first....
May 13, 2009 at 4:32 pm
I think you need to be much more specific!
Deleting one row on a unique clustered index .. really quick
Deleting one row on a nonclustered index .. slightly slower
Deleting one row...
May 13, 2009 at 4:17 pm
Further to this I just got the following reply from Paul White on another thread:
Paul White (4/30/2009)
May 1, 2009 at 3:20 am
Grant, thanks very much for your input too, I really appreciate the help.
Tim
May 1, 2009 at 3:01 am
Paul White (4/30/2009)
Tim,You should use the event SQL:StmtRecompile instead of SP:Recompile in 2005 and later.
I actually abridged my profile too much! I was capturing both events, and I...
May 1, 2009 at 3:00 am
Thanks Mike, I'm glad the link was useful. I agree with your DMV experience, I got just the same effect.
One thing I didn't mention in the previous post is the...
April 29, 2009 at 9:35 am
I tried this on a SQL 2005 database migrated from SQL 2000 and had this exact problem. I wanted to do small shrinks as the database in question is a...
April 29, 2009 at 6:36 am
Viewing 15 posts - 151 through 165 (of 242 total)