Comments
Sort by recent activity
Maybe one of my other settings is affecting this.
Here are the settings I am using:
Operating System: Windows XP SP2
SQL Server Version: SQL Server 2005 SP2 (9.0.3054)
Candidates Settings:
All possible Completion Keys are checked: ("Enter", "Tab", "Spacebar", "Dot", "Comma", "Closing bracket", "Parenthesis")
All possible Join Conditions are checked: ("Include matching column names", "Include matching data types")
"Apply case-sensitive sort order" is NOT checked
"Show objects for specified owner or schema" is checked
All checkboxes in Other Objects are checked ("Include variables in the candidate list", "Include system objects in the candidate list")
Style Settings:
"Qualify object names" is checked
"Qualify column names" is NOT checked
"Surround with brackets" is NOT checked
"Insert parentheses for built-in functions and data types" is checked
"Reserved keywords" is set to "Force UPPERCASE"
"Built-in functions" is set to "Force UPPERCASE"
"Built-in data types" is set to "Force lowercase"
Auto Insert Settings:
"Enable TAB to expand columns after SELECT" is checked
"Use new line for each column" is checked
"Insert object definition on ALTER" is checked
"Insert parameters for functions and stored procedures" is checked
"Insert hints for data types" is checked
In the "Automatic Closing Characters" section, the following are checked: ("Parenthesis", "Bracket" and "Single quotation mark")
In the "Automatic Closing Characters" section, the following are NOT checked: ("Double quotation mark" and "Comment mark") / comments
Maybe one of my other settings is affecting this.
Here are the settings I am using:
Operating System: Windows XP SP2
SQL Server Version: SQL Server 2005 SP2 (9.0.3054)
Candidates Settings:
All poss...
This is my version number: 3.1.0.39. / comments
This is my version number: 3.1.0.39.
It seems to have something to do with the DMVs, because I get the same behavior with this script that I use to monitor my SQL Backup jobs:
SELECT er.session_id, program_name, er.command, er.sql_handle, er.start_time, er.status, er.percent_complete, er.blocking_session_id
FROM sys.dm_exec_sessions es INNER JOIN sys.dm_exec_requests er
ON es.session_id = er.session_id
CROSS APPLY sys.dm_exec_sql_text(er.sql_handle)
WHERE program_name like '%SQB%'; / comments
It seems to have something to do with the DMVs, because I get the same behavior with this script that I use to monitor my SQL Backup jobs:
SELECT er.session_id, program_name, er.command, er.sql_han...
Bart Read wrote:
Does anybody else experience this or have any information on how we could reproduce it please?
Thanks,
Bart
Yes, I am also experiencing this error.
In my case, it is always happening when I work with the "sys.dm_db_index_physical_stats" Dynamic Management View. The syntax of the command is as follows:
SELECT *
FROM sys.dm_db_index_physical_stats(DB_ID(N'<UserDatabaseName>
', NULL, NULL, NULL, 'LIMITED');
As soon as I enter the left parenthesis, the exception is thrown. It also happens if I click or type anything inside the parentheses of an existing script of this command.
My machine runs Windows XP Professional SP2 (Build 2600) and SQL Server 2005 SP1 with Cumulative Hotfix KB918222. The SQL Server build number with this hotfix is 9.0.2153. I have downloaded all current Windows updates other than SP1 for Visual Studio 2005. / comments
Bart Read wrote:
Does anybody else experience this or have any information on how we could reproduce it please?
Thanks,
Bart
Yes, I am also experiencing this error.
In my case, it is always hap...
Thanks for the informatin Petey, I was having the same problem.
I just want to add one thing: remember that each installation will create its own SQL Backup Agent. The name of the agent will be "SQL Backup Agent-<INSTANCE_NAME>. You need to start this agent after installation.
I discovered this when I attempted to configure SQL Backup for the instance. All the tabs within the Option dialog box were greyed out, and I couldn't figure out why. I figured it out when I tried to do a Backup from the GUI and got an error message that the SQL Backup Agent service could not be started. Once I started the agent, I could set the Options. / comments
Thanks for the informatin Petey, I was having the same problem.
I just want to add one thing: remember that each installation will create its own SQL Backup Agent. The name of the agent will be "S...
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
I tried
EXEC sqbsetlogin '',''
and
sqbsetlogin '',''
I got the error both times. Any ideas? / comments
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
I tried
EXEC sqbsetlogin '',''
and
sqbsetlogin '',''
I got the error both...
Are you working towards making it work in tandem with the native SQL Server IntelliSense? I think the current inability to work together with the native IntelliSense is a major drawback of the product. / comments
Are you working towards making it work in tandem with the native SQL Server IntelliSense? I think the current inability to work together with the native IntelliSense is a major drawback of the pro...
Okay, that confirms what I experienced. I tried running the backup without sysadmin privileges and I received an error message about the inability to use a virtual device without being a member of sysadmin. I just wanted to ask people who have been using the product for a while if there was any workaround for that issue.
Thanks for your assistance. / comments
Okay, that confirms what I experienced. I tried running the backup without sysadmin privileges and I received an error message about the inability to use a virtual device without being a member of...