Viewing 15 posts - 3,556 through 3,570 (of 49,571 total)
Filters in indexes don't allow OR.
I'm not sure if what you're trying to do can be done in a filtered index. They have to be simple filters.
February 19, 2016 at 4:59 am
Google down? 😉
First search results: http://www.investopedia.com/terms/s/stump-the-chump.asp
February 19, 2016 at 4:56 am
Speeding up changing results implies things were running on two sessions. Within a single session, SQL executes statements strictly in sequence. So if you have code of:
SELECT <something>
INSERT <Something else>
...
February 19, 2016 at 4:54 am
SQLAssAS (2/19/2016)
Is there still a performance advantage of doing this in a VM environment if we just have 1 raid 5 pool of disk?
No.
There may be a management benefit...
February 19, 2016 at 2:46 am
Are they hypothetical indexes (from DTA)? Don't know if those show un with helpindex, but they won't in SSMS.
Try querying sys.indexes directly.
February 19, 2016 at 2:16 am
SQLRNNR (2/18/2016)
February 19, 2016 at 2:14 am
Fixing this will require either changing the query or changing the index. Can you do either?
February 18, 2016 at 8:05 am
There's lots of things that will spill to TempDB, and even if there's available buffer pool memory they get written out (kept in memory, but written out). But if you're...
February 18, 2016 at 7:05 am
Faulty SSD? Faulty switch/controller/cables (as applicable)?
February 18, 2016 at 6:40 am
Not possible. SQL executes statements strictly sequentially when they're in the same batch (which a procedure is).
Sure another process isn't somehow deleting B? Or is the insert into B failing...
February 18, 2016 at 6:39 am
Huh?
A clustered SQL Server doesn't care whether the passive node is down or not. Passive node is passive, there's no SQL instance running on it.
As I've already explained, a cluster...
February 18, 2016 at 6:33 am
No.
Cluster failover is NOT live migration. Failover is just an automatic version of stopping a SQL service on one node and starting it on another.
February 18, 2016 at 5:38 am
Wrap it in a transaction and do the insert WITH TABLOCKX. Nasty for concurrency, but as long as you don't do this often may be fine.
February 18, 2016 at 5:35 am
When the active node fails and the cluster fails over, SQL restarts on the new node. Part of that restart is crash recovery. During crash recovery any uncommitted transactions (uncommitted...
February 18, 2016 at 5:14 am
Could be anything, could be the procedures that the replication uses (which it creates itself), could be connection properties, could be a bunch of other stuff.
Why not create a stored...
February 18, 2016 at 5:06 am
Viewing 15 posts - 3,556 through 3,570 (of 49,571 total)