Viewing 15 posts - 13,591 through 13,605 (of 59,063 total)
November 22, 2017 at 8:12 am
November 22, 2017 at 8:03 am
This might fitting into your requirement.
November 22, 2017 at 7:27 am
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...
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...
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...
November 22, 2017 at 6:23 am
November 21, 2017 at 9:55 pm
Hmmm... I haven't tried it but perhaps a BIGINT Sequence would work here.
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.
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...
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...
November 21, 2017 at 4:59 pm
The non-premium rates have a charge for every 10,000 "transactions". They don't define what a transaction is, though, or at least I've not found it yet. If a "transaction" is...
November 21, 2017 at 4:56 pm
November 21, 2017 at 4:49 pm
Viewing 15 posts - 13,591 through 13,605 (of 59,063 total)