Home Dashboard Directory Help
Refine Search Results
Status
Votes
Total Votes (at least)
Workarounds
Total Workarounds (at least)
Validations
Total Validations (at least)
Comments
Total Comments (at least)
Time
Created in the last (days)
Updated in the last (days)
Product Search Results
Sort By:
You searched for: items submitted by Hugo Kornelis for this product (signing in could show even more results)
Showing 1 - 10 of 35 Previous 123 Next

1
0
Sign in
to vote
From Connection: SQL Server
The Books Online topic about TOP says in the opening paragraph that a query with TOP but without ORDER BY "returns the first N number of random rows". The term random is incorrect. It implies that al…
Created on 9/19/2012 (updated 107 weeks ago) | 0 validations | 0 workarounds | 1 comment | feedback id: 763576  | 
Closed
as Fixed Help for as Fixed
2
1
Sign in
to vote
From Connection: SQL Server
When creating a stored procedure that contains a BEGIN keyword, immediately followed by a syntax error, that error is not detected. The stored procedure is created and can even be executed, allthough …
Created on 8/28/2012 (updated 87 weeks ago) | 2 validations | 1 workaround | 2 comments | feedback id: 759946  | 
Closed
as Fixed Help for as Fixed
24
1
Sign in
to vote
From Connection: SQL Server
The documentation in Books Online for the ISDATE function says that the argument has to be "a character string or expression that can be converted to a character string". This is not true. When called…
Created on 8/28/2012 (updated 1 week ago) | 13 validations | 0 workarounds | 5 comments | feedback id: 759944  | 
Closed
as Fixed Help for as Fixed
10
1
Sign in
to vote
From Connection: SQL Server
Even when SQL Server knows the cost of executing a scalar user-defined function, that cost is not incorporated in the cost of an exeution plan that involves calling the function. This effectively cri…
Created on 5/25/2012 (updated 6 days ago) | 3 validations | 0 workarounds | 4 comments | feedback id: 744019  | 
Closed
as Won't Fix Help for as Won't Fix
5
0
Sign in
to vote
From Connection: SQL Server
When I try to build a columnstore index on a table that has a clustered index on a uniqueidentifier column, that column will be added even if I don't specify it. Since uniqueidentifier is not a suppor…
Created on 2/17/2012 (updated 34 weeks ago) | 1 validation | 0 workarounds | 2 comments | feedback id: 725468  | 
Closed
as By Design Help for as By Design
2
0
Sign in
to vote
From Connection: SQL Server
The syntax diagram for CREATE TABLE in Books Online is incorrect. The first few lines currently read: CREATE TABLE [ database_name . [ schema_name ] . | schema_name . ] table_name ( { <colum…
Created on 3/10/2011 (updated 119 weeks ago) | 0 validations | 0 workarounds | 2 comments | feedback id: 650713  | 
Closed
as Fixed Help for as Fixed
3
0
Sign in
to vote
From Connection: SQL Server
A query that includes COUNT(*) on a subquery that should generate an error, may sometimes return 1. I believe this is due to the optimizer shortcircuiting some of the steps, based on the assumption t…
Created on 4/6/2010 (updated 236 weeks ago) | 0 validations | 0 workarounds | 2 comments | feedback id: 549105  | 
Closed
as By Design Help for as By Design
35
0
Sign in
to vote
From Connection: SQL Server
The SQL Server engine chooses an execution plan for COALESCE((subquery), 1) where the subquery is executed twice. This is not only bad for performance, it can also cause incorrect results to be return…
Created on 3/31/2010 (updated 20 weeks ago) | 10 validations | 1 workaround | 4 comments | feedback id: 546437  | 
Closed
as By Design Help for as By Design
8
0
Sign in
to vote
From Connection: SQL Server
A CHECK constraint that uses a user-defined function to count rows in the target table can forbid correct modifications. It appears as if the rows are modified and checked one by one, instead of fi…
Created on 3/27/2010 (updated 142 weeks ago) | 1 validation | 0 workarounds | 3 comments | feedback id: 545075  | 
Closed
as Won't Fix Help for as Won't Fix
2
0
Sign in
to vote
From Connection: SQL Server
The MERGE statement can prevent the possibility of inserting rows that already exist in the destination, but it can not prevent errors caused by duplicates in the source data. According to Books On…
Created on 9/10/2008 (updated 293 weeks ago) | 0 validations | 0 workarounds | 1 comment | feedback id: 366994  | 
Closed
as By Design Help for as By Design
Showing 1 - 10 of 35 Previous 123 Next