Home
Dashboard
Directory
Help
Sign in
Microsoft
Connect
Your feedback improving Microsoft products
Search
Feedback
All Connect
SQL Server Home
Downloads
Feedback
Surveys
Refine Search Results
Status
All
Active
Resolved
Closed
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)
Scope
All Feedback
Your Feedback
Product Search Results
Sort By:
Newest
Last Updated
Up-Votes
Total Votes
Title (A-Z)
Title (Z-A)
Down-Votes
Oldest
You searched for:
items submitted by Tom Cooper for this product
(
signing in
could show even more results)
Bugs (5)
Suggestions (0)
Showing
1
-
5
of
5
Previous
1
Next
2
0
Sign in
to vote
Documentation says filtered indexes automatically include primary key, that is incorrect
- by
Tom Cooper
From Connection:
SQL Server
The documentation (http://technet.microsoft.com/en-us/library/cc280372.aspx) states in the Limitations and Restrictions section: "The primary key of the table does not need to be a key or included col…
Created on 1/4/2013 (updated 18 weeks ago)
|
0 validations
|
0 workarounds
|
2 comments
|
feedback id: 775841
|
Closed
as Fixed
3
0
Sign in
to vote
Coalesce and IsNull give incorrect 8152 error if first parameter is a string expression containing a null operand and second parameter is nvarchar > 4000 characters
- by
Tom Cooper
From Connection:
SQL Server
If you use Coalesce (or use IsNull) and the first parameter is an string concatenation expression with string constants and an nvarchar(max) variable which contains null, and the second parameter is a…
Created on 10/7/2011 (updated 22 weeks ago)
|
0 validations
|
2 workarounds
|
3 comments
|
feedback id: 693614
|
Closed
as By Design
2
0
Sign in
to vote
Computed time(7) column returns an error when selected
- by
Tom Cooper
From Connection:
SQL Server
A valid expression computing a time(7) value works if included in a SELECT query, but returns an error if used for a computed column.
Created on 7/31/2010 (updated 118 weeks ago)
|
0 validations
|
0 workarounds
|
2 comments
|
feedback id: 581976
|
Closed
as Fixed
4
1
Sign in
to vote
Users with Select permission on one column in a table get errors from IF EXISTS (SELECT * FROM <table>)
- by
Tom Cooper
From Connection:
SQL Server
If a user has select permission on some but not all columns in a table, then if that user does an IF EXISTS(SELECT * FROM <table>) the user will get a permission violation. This should not happen sin…
Created on 2/13/2010 (updated 170 weeks ago)
|
0 validations
|
1 workaround
|
5 comments
|
feedback id: 533491
|
Closed
as By Design
0
0
Sign in
to vote
Query optimizer chooses a very inefficient plan
- by
Tom Cooper
From Connection:
SQL Server
In certain cercumstances, detailed in "Steps to Reproduce", the generated plan is very inefficient and does not scale. If a temporary table is built by doing a SELECT INTO and then that table is used…
Created on 7/3/2009 (updated 156 weeks ago)
|
0 validations
|
0 workarounds
|
2 comments
|
feedback id: 472398
|
Closed
as Won't Fix
Showing
1
-
5
of
5
Previous
1
Next
© 2013 Microsoft Corporation. All rights reserved.
Microsoft Connect Terms of Use
|
Trademarks
|
Privacy Statement
Microsoft
Please wait...