Viewing 15 posts - 16,411 through 16,425 (of 59,101 total)
Nightly restore of 2 main production databases:
DB1: 515GB, 13.35% free space, 10.0GB Log file
DB2: 76GB, 36.69% free space, 33.5GB Log file (yeah... I know)
Total time to restore including...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 12:05 pm
Eirikur Eiriksson (11/4/2016)
crookj (11/4/2016)
Luis Cazares (11/4/2016)
djj (11/4/2016)
Ed Wagner (11/4/2016)
Revenant (11/4/2016)
Hugo Kornelis (11/4/2016)
Luis Cazares (11/4/2016)
MatchWinner
Medal
Olympics
Olympian
Zeus
Orion
The Hunter
Betelgeuse
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 11:57 am
Luis Cazares (11/4/2016)
Jeff Moden (11/3/2016)
Luis Cazares (11/3/2016)
I know it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 11:54 am
With the understanding that it clears out on a restart of the SQL Service, you could also look at sys.dm_db_index_usage_stats. It won't differentiate between INSERTs and UPDATEs but it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 8:50 am
2.3 TB in an hour and a couple of minutes. On a good night, it takes about 56 minutes. And that's to NAS storage, which is a huge...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 7:52 am
If the number itself is not important, the an easier way to do this might be to add an identity column to the table and create a persisted computed column...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 7:23 am
Partitioning a table isn't going to help much with stats unless you have 2012 or greater and are willing to accept the default sampling rate, which I'm usually not willing...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 4, 2016 at 7:14 am
I don't know if you've ever read the following but it might give you some hints about why you might not want to drop the Clustered Index prior to loading...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 9:26 pm
curious_sqldba (11/3/2016)
Folks just wanted to know if anyone has experience maintaining indices and statistics on big tables ( 600 GB +).
Yes, do you have any experience there?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 8:35 pm
If these tables are of any size, definitely consider loading them with at least the Clustered Index already in place. To do it quickly and without blowing the log...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 8:31 pm
I didn't realize that you were trying to shred the XML of packages... certainly not so many of them. I'm no Ninja at XML either and apologize for my...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 7:43 pm
Luis Cazares (11/3/2016)
I know it's possible but my skills...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 7:20 pm
Why not just properly shred the XML and store the results in proper tables? Makes lookups real easy. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 11:38 am
scott.laird (11/3/2016)
A stored procedure is used to create the pivot, using dynamic SQL.
The SP is using EXEC...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 11:32 am
Where I work, we actually have to sign off on a monthly notice as to whether or not we are aware of anything "questionable" that could lead to the proverbial...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 3, 2016 at 11:09 am
Viewing 15 posts - 16,411 through 16,425 (of 59,101 total)