Reputation
31,468
Next tag badge:
484/400 score
71/80 answers
Badges
8 79 132
Newest
 Enlightened
Impact
~928k people reached

Jan
1
comment Error 18456 State 38 on Deleted Databases
Error 18456 is login failed isn't it?
Jan
1
comment Understanding statistics, execution plans, and 'ascending key problem'
RECOMPILE wouldn't cause a stats update anyway.
Jan
1
comment Store Repeated Data
So the proposed new structure is 100 heap tables. Each heap containing 1bn rows with a single column with a bigint value? What kind of queries do you do against this data? Purely aggregation? Or are there other columns too?
Dec
30
comment What do these parameters mean at the beginning of my SQL Server query plan?
Are suggestions 1 and 2 deliberately the same?
Dec
30
comment What is the cause of this problem with CONVERT()?
@MaxVernon I didn't find it documented. I'm not sure whether or not this is a standard (e.g. IEEE) format but it was easy to see the first two bytes by trial and error. E.g declare a variable of type numeric(38,0) and convert it to varbinary.
Dec
30
revised Get the pais_id not associated to fabricante_distribuidor_id and producto_solicitud_id, the opposite from SELECT query
deleted 171 characters in body
Dec
30
comment Can rebuilding indexes cause worse performance after the rebuild is finished?
And before doing that have a look at STATISTICS IO read ahead reads/physical reads to see if the 6 minutes query is even reading from disc at all.
Dec
30
comment Can rebuilding indexes cause worse performance after the rebuild is finished?
Agree with @Reaces. Rebuilding indexes will have updated stats and invalidated existing query plans. Maybe you were unlucky with the parameter values passed when the new plan was compiled.
Dec
30
revised Can rebuilding indexes cause worse performance after the rebuild is finished?
edited title
Dec
30
comment What is the cause of this problem with CONVERT()?
The first byte is scale (0x01 = 1), The second byte is precision (0x00 = 0), The final byte is the value (0x01 = 1). Not sure what bytes three and four are for. The sign is in there but that doesn't need two bytes. Certainly flipping that bit doesn't seem to have affected anything.
Dec
29
comment Email address unique or primary key?
No. A unique constraint is treated slightly differently and has some additional metadata and additional restrictions compared to a unique index but SQL Server allows either to be used in an FK.
Dec
29
comment Email address unique or primary key?
In SQL Server you can reference a unique index as a FK.
Dec
28
comment The SQL server Log folder is expanding because of the SQL Dump files (what to do with it ?)
Why are you accumulating so many mini dump files? Is the service constantly crashing?
Dec
27
answered MySQL WHERE if NULL select another column
Dec
27
revised MySQL WHERE if NULL select another column
added 22 characters in body
Dec
26
revised Converting a Unicode value to a non-Unicode value (SQL Server)
added 8 characters in body
Dec
24
comment Reasons for avoiding large ID values
Though if you do have a legitimate expectation that you may need bigint you'll probably thank yourself for deciding that in advance rather than needing to add this in to a table with billions of rows.
Dec
18
awarded  Enlightened
Dec
18
awarded  Nice Answer
Dec
17
comment In SQL Server, can I guarantee an order without an explicit ORDER BY clause when an index seek is forced on a table with only a clustered index?
@JeroenMostert - IGNORE_DUP_KEY could do that.