Viewing 15 posts - 7,336 through 7,350 (of 7,608 total)
The most important performance aspect of a table is determining the correct clustered index.
Absolutely, and what I want is one that is narrow - doesn't make nonclustered indexes larger than...
July 6, 2012 at 12:16 pm
GilaMonster (7/6/2012)
There's only one clustered index, multiple nonclustered indexes, clustered index to organise the table, nonclusters to support the queries.
Every column added to a query invalidates the existing covering index...
July 6, 2012 at 10:49 am
An integer column defined as identity (a very good and popular choice for clustered index) is 4 bytes.
It's certainly popular, but most often not good. The no-thought identity as...
July 6, 2012 at 8:40 am
CELKO (7/1/2012)[/bCode should be in Standard SQL as much as possible and not local dialect.
Given that this a SQL Server forum, SQL server dialect is fine. In particular,...
July 5, 2012 at 4:26 pm
Lynn Pettis (7/3/2012)
ScottPletcher (7/3/2012)
Also you have 2 very big indexes.One has 10 columns and other has 9 columns .Table just has 12 columns.
It's a pretty sure bet you have the...
July 3, 2012 at 3:45 pm
Also you have 2 very big indexes.One has 10 columns and other has 9 columns .Table just has 12 columns.
It's a pretty sure bet you have the wrong clustered index....
July 3, 2012 at 1:56 pm
Lynn Pettis (7/3/2012)
alter table MyTable
Add Constraint [MyPrimaryKey] Primary Key (MyColumn)
WITH (FILLFACTOR = 75, ONLINE = ON, PAD_INDEX = ON);
Be sure to verify the complete syntax in...
July 3, 2012 at 1:49 pm
During the load in the where clause there is a selection (or join) on the logical key and the row must be actual (Y).
If the logical key nonclus index needs...
June 28, 2012 at 10:25 am
Also, do a
DBCC UPDATEUSAGE
on the table. Heaps seem to report ridiculously incorrect page totals too often for comfort. I've had SQL telling me that a single...
June 28, 2012 at 9:53 am
CELKO (6/27/2012)
ScottPletcher (6/27/2012)
Regarding date formatting, I'd suggest using 'YYYYMMDD', which is foolproof on SQL Server, rather than 'YYYY-MM-DD', which can fail depending on specific settings in SQL Server.
NO! That is...
June 27, 2012 at 4:11 pm
Eugene Elutin (6/27/2012)
Mike John (6/27/2012)
Once committed it is committed....
Not for nested transactions, check this one:
begin transaction outerOne
update Table1 set Col1 = 'booo' where id =1 ...
June 27, 2012 at 3:54 pm
Code looks OK to me.
Regarding date formatting, I'd suggest using 'YYYYMMDD', which is foolproof on SQL Server, rather than 'YYYY-MM-DD', which can fail depending on specific settings in SQL Server.
June 27, 2012 at 3:46 pm
You could have tempdb data files on both RAID1s for performance reasons, simulating something of a faux RAID 10, recoverability obviously not being a factor for tempdb.
Depending on...
June 27, 2012 at 10:34 am
The contention (I think) is where some folks latched onto something you said that implied you knew how to recover from a lost array in a 2xRAID1 setup with no...
June 26, 2012 at 4:58 pm
I think this series of articles is pretty good, and yielded some interesting results about RAID:
http://www.kendalvandyke.com/2009/02/disk-performance-hands-on-part-6-raid.html
That's not to say this article is the last word on RAID or anything. ...
June 26, 2012 at 4:48 pm
Viewing 15 posts - 7,336 through 7,350 (of 7,608 total)