Viewing 15 posts - 5,386 through 5,400 (of 49,571 total)
Brent Leslie (7/8/2015)
2015-05-05 is then loaded, meaning all the data for 06 to 08 needs to be shifted.
Err, no. You will probably get some page splits, but SQL doesn't re-insert...
July 8, 2015 at 12:09 pm
Yes.
Well, you could drop the replication, truncate the table and then reconfigure and initialise the replication, but I doubt that's a feasible option.
July 8, 2015 at 12:02 pm
If you have lots of queries which filter on that date, it may well be a very good place for the clustered index.
Narrow, unique, ever-increasing, unchanging are guidelines, not set-in-stone...
July 8, 2015 at 4:24 am
The ability to directly address more than 2GB of memory.
July 8, 2015 at 2:41 am
While 'nuke from orbit' is a good strategy for some problems, it's not a good strategy when doing index changes, especially clustered index changes. Make such significant changes and you'll...
July 8, 2015 at 2:28 am
No, it'll be automatically dropped as soon as it goes out of scope.
Why are you using a table variable (with it's attendant row estimation problems) over a temp table?
July 8, 2015 at 2:22 am
Casper101 (7/7/2015)
Is it possible to undo/rollback all the code in a proc when a timeout occurs - without using a TRANSACTION?
No. That's what transactions are there for
And if a TRANSACTION...
July 8, 2015 at 1:44 am
preston 34832 (7/7/2015)
Wouldn't it be better to have the OS using vCPU1 as its starting point and SQL Express run on the second vCPU?
No, because the OS isn't bound...
July 8, 2015 at 1:41 am
Contention most likely. Could be blocking, could be other waits. You'll have to analyse and investigate.
July 7, 2015 at 9:19 am
Size of the log and high % use will not cause queries to run slowly.
July 7, 2015 at 5:00 am
SQL!$@w$0ME (7/6/2015)
This particular db is almost 450gb in size.
So a fairly small database still.
SQL data files max out at 16 TB, not a few GB. You split across drives...
July 6, 2015 at 2:01 pm
Why are you worried about 70GB files growing 'too much'?
July 6, 2015 at 1:39 pm
I'm not. The cardinality estimator changed completely in SQL 2014. Most queries have an improved performance, but some do get a degradation.
July 6, 2015 at 9:40 am
Actual Number of Rows = Rows in the table spool * Number of Executions. It's the total number that have been read out of the spool, not the number inserted.
Can...
July 6, 2015 at 8:55 am
Viewing 15 posts - 5,386 through 5,400 (of 49,571 total)