Viewing 15 posts - 17,866 through 17,880 (of 59,069 total)
TheSQLGuru (4/14/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2016 at 9:30 am
djj (4/13/2016)
crookj (4/13/2016)
Hugo Kornelis (4/13/2016)
Ed Wagner (4/13/2016)
Grumpy DBA (4/12/2016)
crookj (4/12/2016)
BaggerVance
Lance
Carrier
Kitty Hawk
Wright
Being a former submarine sailor, I'll tell you a word that describes those last two entries... TARGET! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2016 at 2:23 am
ThomasRushton (4/14/2016)
Ed Wagner (4/13/2016)
DonlSimpson (4/13/2016)
Luis Cazares (4/13/2016)
Ed Wagner (4/13/2016)
crookj (4/13/2016)
jeff.mason (4/13/2016)
Manic Star (4/13/2016)
Ed Wagner (4/13/2016)
ThomasRushton (4/13/2016)
jeff.mason (4/13/2016)
Revenant (4/13/2016)
Hugo Kornelis (4/13/2016)
djj (4/13/2016)
crookj (4/13/2016)
Hugo Kornelis (4/13/2016)
Ed Wagner (4/13/2016)
Grumpy DBA (4/12/2016)
crookj (4/12/2016)
BaggerVance
Lance
Carrier
Kitty Hawk
Wright
Rong
China
Grove
Dictionary
(of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2016 at 2:21 am
Tava (4/13/2016)
After rebuilding all the indexes that were used it fixed our issue. SP now returns instantly.
If you did REBUILDs instead of just REORGANIZEs, then it's very likely that the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2016 at 2:17 am
It's a funny thing... I no longer reindex or reorganize on my main production box. Log files were getting blown out by the maintenance actions, the database was expanding...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 7:54 pm
sarath.tata (4/13/2016)
I have created a sqlfiddle to help understand my structure and data....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 7:16 pm
Yes. Staging tables... but that's about it. What I've personally encountered is 3rd party database developers that either don't have a clue or believe that the use of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 6:43 pm
140+ files... each file goes to a separate table... etc...
It sounds more like a version of "poor man's replication" of a whole or nearly whole database. I'd recommend talking with...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 6:08 pm
jacksonandrew321 (4/13/2016)
you may need to trigger the database growth event or set alert for the database.
How will that help determine the growth over a year? Why not just sample...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:58 am
Manic Star (4/13/2016)
In SSRS, the matrix report handles this...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:54 am
Eirikur Eiriksson (4/12/2016)
Quick thought, look at Ola Hallengren's maintenance scripts, he has a very good clean up process there😎
Isn't that just for backup files?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:50 am
ChrisM@Work (4/13/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:44 am
Sk1ppy (4/12/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:22 am
LesterF (4/12/2016)
However, there is something I think it's worth sharing. Sometimes developers abuse split functions like these for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 13, 2016 at 8:16 am
cad.delworth (4/12/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 9:16 pm
Viewing 15 posts - 17,866 through 17,880 (of 59,069 total)