Viewing 15 posts - 15,781 through 15,795 (of 49,552 total)
You're probably looking at the fragmentation of the non-leaf levels.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 4:39 pm
Chapter 6
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 1:55 pm
SQL won't let you restore the same log backup twice.
There is absolutely no chance whatsoever of ever being able to miss transactions in the middle or restore transactions twice...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 1:51 pm
Completely false.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 11:50 am
Huh?
The data caching is much the same between 2008 and 2012. Data pages from the data file on disk are cached, query results are not and never have been cached.
How...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 9:04 am
rmudway (11/6/2012)
GilaMonster (11/5/2012)
Doesn't sound right. If the historical data isn't queried, it won;t be in memory, doesn't matter if in one DB or two.
Well... i dont need the historical data...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 9:01 am
sanket kokane (11/5/2012)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 8:59 am
If you want to break the log chain (as truncate only used to do), switch to simple recovery. That's the replacement for the truncate only.
You probably have the active portion...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 6, 2012 at 8:55 am
Task is the currently running query
Session is the total since the session (connection) logged in.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 10:35 pm
sanket kokane (11/5/2012)
What I was mean to say is consider enabling /PAE as your last option.
If running SQL on 32-bit OS with more than 4GB of memory, /PAE is a...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 10:34 pm
shohelr2003 (11/5/2012)
Actually I need to shrink my log file. As my database increases regularly, it slows down my application system.
A large transaction log will not cause performance problems. Free space...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 10:05 pm
Doesn't sound right. If the historical data isn't queried, it won;t be in memory, doesn't matter if in one DB or two.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 10:04 pm
Query results are never cached.
What SQL caches are data pages (to avoid having to read from disk) and execution plans (to avoid having to recompile). in both of those...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 10:03 pm
sanket kokane (11/5/2012)
also as per the above person said never shrink your data file,it makes your indexes completely unused
No, it does not. It fragments indexes, doesn't make them unusable, doesn't...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 8:32 pm
Performance tuning should be done first, not last. Well performing queries are generally more efficient in memory usage.
Database being entirely in memory doesn't automatically mean the queries will be fast.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 5, 2012 at 8:31 pm
Viewing 15 posts - 15,781 through 15,795 (of 49,552 total)