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 Greg Low - Australia for this product (signing in could show even more results)
Showing 1 - 10 of 58 Previous 123 Next

8
0
Sign in
to vote
From Connection: SQL Server
Intellisense warns that an object already exists on a CREATE OR ALTER statement. This is not appropriate.
Created on 1/14/2017 (updated 6 weeks ago) | 1 validation | 0 workarounds | 1 comment | feedback id: 3118798  | 
Closed
as Fixed Help for as Fixed
3
1
Sign in
to vote
From Connection: SQL Server
DROP DATABASE IF EXISTS fails if the database is in use. Checking to see if it is already in use requires first checking if it exists. So this makes the statement as supplied pointless.
Created on 11/1/2016 (updated 11 weeks ago) | 0 validations | 0 workarounds | 2 comments | feedback id: 3110070  | 
Active
1
0
Sign in
to vote
From Connection: SQL Server
If a table is renamed in a T-SQL script, Intellisense becomes completely confused.
Created on 10/19/2016 (updated 31 weeks ago) | 0 validations | 0 workarounds | 0 comments | feedback id: 3107410  | 
Active
1
0
Sign in
to vote
From Connection: SQL Server
If you use the advisor on a proc that contains subqueries in UPDATE or DELETE statements, the error flagged is that subqueries are not supported. This is not true. I gather it is only subqueries in UP…
Created on 10/19/2016 (updated 20 weeks ago) | 0 validations | 0 workarounds | 1 comment | feedback id: 3107393  | 
Active
2
0
Sign in
to vote
From Connection: SQL Server
If a stored procedure uses the IIF function, the Native Compilation Advisor in SSMS complains they have used a CASE statement. This is confusing to users. The error should perhaps say "CASE or IIF".
Created on 8/12/2016 (updated 41 weeks ago) | 0 validations | 0 workarounds | 0 comments | feedback id: 3042394  | 
Active
13
0
Sign in
to vote
From Connection: SQL Server
I have a stored procedure that removes the temporal nature of a table so that I can update the history directly. I cannot catalog a stored procedure that is intended for use only when the temporal na…
Created on 3/21/2016 (updated 16 weeks ago) | 0 validations | 2 workarounds | 0 comments | feedback id: 2500716  | 
Active
1
0
Sign in
to vote
From Connection: SQL Server
In the code attached, you can see that THROW is flagged as incorrect. The syntax however is valid and works fine. Note: This was tested on RC1 not CTP3 but that option is not available in the dropd…
Created on 3/21/2016 (updated 61 weeks ago) | 0 validations | 0 workarounds | 0 comments | feedback id: 2500146  | 
Active
1
0
Sign in
to vote
From Connection: SQL Server
When you use the option to drop a database in SSMS, and select the option to close existing connections, if you script the command instead of executing it, the closing of existing connections is not s…
Created on 3/15/2016 (updated 62 weeks ago) | 0 validations | 0 workarounds | 0 comments | feedback id: 2476476  | 
Active
3
0
Sign in
to vote
From Connection: SQL Server
When SQL Server Management Studio is used to generate SQL scripts, and the option is chosen to script statistics and histograms, if a table with a filtered index is being scripted, a WHERE clause is a…
Created on 8/19/2015 (updated 83 weeks ago) | 0 validations | 0 workarounds | 0 comments | feedback id: 1689631  | 
Active
3
0
Sign in
to vote
From Connection: SQL Server
When the New Login dialog is used to create a new SQL Server Login in SSMS, if the new user is not a db_owner but is given access to a database in some other role, an error is returned.
Created on 7/14/2015 (updated 43 weeks ago) | 1 validation | 0 workarounds | 2 comments | feedback id: 1547066  | 
Closed
as Fixed Help for as Fixed
Showing 1 - 10 of 58 Previous 123 Next