Reputation
473
Top tag
Next privilege 500 Rep.
Access review queues
Badges
7 18
Newest
 Constituent
Impact
~21k people reached

  • 0 posts edited
  • 9 helpful flags
  • 69 votes cast
1d
awarded  Constituent
Jul
31
awarded  Notable Question
Jul
27
awarded  Caucus
May
20
awarded  Notable Question
May
20
awarded  Custodian
May
20
reviewed Approve Why 0 is equal to empty string?
May
19
accepted Why 0 is equal to empty string?
May
19
comment Why 0 is equal to empty string?
Find it. The SQL Server is converting the empty string to INT which is 0. So, I need to check for '0' = '' instead.
May
19
asked Why 0 is equal to empty string?
May
15
awarded  Popular Question
Apr
21
accepted How many records should be deleted when batch delete is used?
Apr
20
revised How many records should be deleted when batch delete is used?
added 323 characters in body
Apr
20
revised How many records should be deleted when batch delete is used?
added 7 characters in body
Apr
20
comment How many records should be deleted when batch delete is used?
@MarkSinkinson Yes, I am sorry - it is the target table.
Apr
20
revised How many records should be deleted when batch delete is used?
edited body
Apr
20
revised How many records should be deleted when batch delete is used?
edited body
Apr
20
asked How many records should be deleted when batch delete is used?
Apr
16
comment How to optimize STDistance execution?
Yes, I have created such. But the query optimizer is not using it. If I use a hint like this WITH (INDEX(SPATIAL_idx_test)) I am getting the following error - Msg 8635, Level 16, State 4, Line 78 The query processor could not produce a query plan for a query with a spatial index hint. Reason: Spatial indexes do not support the comparator supplied in the predicate. Try removing the index hints or removing SET FORCEPLAN.
Apr
16
asked How to optimize STDistance execution?
Mar
30
comment Storing IP addresses - varchar(45) vs varbinary(16)
If it the case was only for IPv4 I guess I would convert the address to INT and used the field as index key. But for IPv6 I need to use two BIGINT fields and I prefer to store the value in one field - seems to me more natural.