Viewing 15 posts - 7,156 through 7,170 (of 7,614 total)
Typically customer codes are sequential. Since they're not here, that would definitely make the clustering key choice much more difficult.
If customer code is (almost) always used for lookups/processing, you...
October 3, 2012 at 8:43 am
Eugene Elutin (10/2/2012)
ScottPletcher (10/2/2012)
sql-lover (10/2/2012)
bteraberry (10/2/2012)
ScottPletcher (10/2/2012)
Maybe I'm missing something.Why not just ALTER the column to be a bigint instead of an int?
He said these are very big tables. ...
October 3, 2012 at 8:29 am
sql-lover (10/2/2012)
bteraberry (10/2/2012)
ScottPletcher (10/2/2012)
Maybe I'm missing something.Why not just ALTER the column to be a bigint instead of an int?
He said these are very big tables. Altering the column...
October 2, 2012 at 5:24 pm
sql-lover (10/2/2012)
ScottPletcher (10/2/2012)
Maybe I'm missing something.Why not just ALTER the column to be a bigint instead of an int?
NO way! Because downtime! Why do you think that I am taking...
October 2, 2012 at 5:18 pm
CELKO (10/1/2012)
October 2, 2012 at 5:15 pm
SELECT *
FROM dbo.CustomerPurchase cp
WHERE
cp.PurchaseDate = '20120601 00:00:00.000' AND
EXISTS(
SELECT 1
...
October 2, 2012 at 5:09 pm
Some other thoughts/possibilities:
Rather than export and then import, it should be faster to just directly INSERT INTO the new table, naturally doing a table lock on the new table.
Pre-allocate enough...
October 2, 2012 at 5:02 pm
bteraberry (10/2/2012)
ScottPletcher (10/2/2012)
Maybe I'm missing something.Why not just ALTER the column to be a bigint instead of an int?
He said these are very big tables. Altering the column means...
October 2, 2012 at 4:47 pm
dwain.c (9/26/2012)
Using it, I'd like to offer a slightly less verbose solution:
SELECT *, WaitTime=DATEDIFF(minute
,CAST(check_in AS TIME)
,CAST(STUFF(appt_time, 3, 0,...
October 2, 2012 at 4:26 pm
Maybe I'm missing something.
Why not just ALTER the column to be a bigint instead of an int?
October 2, 2012 at 4:14 pm
SQL Server is optimized to do table lookups, whereas CASE statements are comparatively very slow.
Therefore, I suggest using a lookup table, as suggested by others. You absolutely want to...
October 2, 2012 at 4:11 pm
I wouldn't duplicate l lot of columns for a covering index w/o real research showing it was 100% necessary.
You should consider the possibility of clusterting tableB on fk_id, but that...
October 2, 2012 at 4:00 pm
Eugene Elutin (10/2/2012)
[
...
Is this statement true? If so is it better to use Guid or BIGINT?
It depends, but usually BIGINT is better.
Another question, related to keys... If a table uses...
October 2, 2012 at 3:51 pm
Ellen-477471 (10/2/2012)
I've searched for this...
October 2, 2012 at 9:38 am
Viewing 15 posts - 7,156 through 7,170 (of 7,614 total)