Viewing 15 posts - 13,621 through 13,635 (of 59,095 total)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 8:20 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 8:15 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 8:12 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 8:03 am
This might fitting into your requirement.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 7:27 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 7:19 am
To answer the immediate question...
I've also seen the rest of the code on your other posts. You're accumulating the information for each database in the global temporary table...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 6:54 am
If your system has a SAN, most SANs have some option to do a SAN "Snapshot" either as a built in or optional feature.
I still think a restore...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 6:30 am
See that DISTINCT? Figure out which join(s) are causing the need for that and fix it. That will almost certainly be the root of your performance problem. If you want...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 6:23 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2017 at 6:14 am
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2017 at 9:55 pm
Hmmm... I haven't tried it but perhaps a BIGINT Sequence would work here.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2017 at 9:10 pm
Put the IDENTITY column back on the table and call it a day. It wasn't as irrelevant as everyone thought.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2017 at 8:53 pm
If finding rows by birth month without regard to year or day is something important, it's probably worthwhile to materialize the birth month in the table using a persisted computed...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2017 at 8:46 pm
It sounds like a classic case of the bad kind of parameter sniffing. My first step on something that handles that many rows would be to add OPTION (RECOMPILE) to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2017 at 4:59 pm
Viewing 15 posts - 13,621 through 13,635 (of 59,095 total)