Comments
Sort by recent activity
I'm getting the same problem
Adding: with SQL Prompt disabled, if I navigate to any SQL Prompt item in QA menu (ex. Options) I receipt the Microsoft .NET Framework error box (Unhandled exception has ocurred... The following elements are not closed: Description, Snippet, Snipets, SnippetManager. Line 105, position 52".
In details buttons, bring to me
"See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Xml.XmlException: Unexpected end of file has occurred. The following elements are not closed: Description, Snippet, Snippets, SnippetManager. Line 105, position 52.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.ThrowUnclosedElements()
at System.Xml.XmlTextReaderImpl.ParseElementContent()"
And much more .
Win XP portuguese-brasilian + sp2 . 1gb ram.
QA version: 8.00.2039 / comments
I'm getting the same problem
Adding: with SQL Prompt disabled, if I navigate to any SQL Prompt item in QA menu (ex. Options) I receipt the Microsoft .NET Framework error box (Unhandled exception ha...
In time...
It only heappens when I alredy have other sentences at the query analyzer window.
If I clear all my script in the window, this problem don't appear, but, if this is my second statement, I get the problem. / comments
In time...
It only heappens when I alredy have other sentences at the query analyzer window.
If I clear all my script in the window, this problem don't appear, but, if this is my second statement, ...
Hi.
Maybe a beta version without the limitation of SQL Prompt only working in the first query analyzer window. It is complicating a lot the tests in a production environment.
Regards
Esio / comments
Hi.
Maybe a beta version without the limitation of SQL Prompt only working in the first query analyzer window. It is complicating a lot the tests in a production environment.
Regards
Esio
Sometimes, using the first windos opened, but changing the database (using use <db> or selecting the other database in Database List, SQL Prompt show objects from older database.
If I change the application focus (using alt + tab), when I back to query analyzer, SQL Prompt show the correct objects / comments
Sometimes, using the first windos opened, but changing the database (using use <db> or selecting the other database in Database List, SQL Prompt show objects from older database.
If I change the ap...
The onwer should appear.
In the WHERE clause, the candidate list displays fields from tables that are not in the FROM clause. / comments
The onwer should appear.
In the WHERE clause, the candidate list displays fields from tables that are not in the FROM clause.
I'm getting some like this.
If I start to write my sentence, and I press backspace after from, the popup doesn't appear anymore:
ex. select * from (here popup appear for the first time), if I press backspace and delete the space after from, bye bye to pop up...
Ésio Nunes / comments
I'm getting some like this.
If I start to write my sentence, and I press backspace after from, the popup doesn't appear anymore:
ex. select * from (here popup appear for the first time), if I press...
I'm running like a adm, and I'm receiving "No such product group" message. / comments
I'm running like a adm, and I'm receiving "No such product group" message.
I disabled the SQL Prompt before connect to my SAP database.
Ok it isn't bringing any suggests, but it is still reading the schema for the database and consuming to many memory : 414MB for Ssms.exe while reading the schema and after some moments it shrink to some megabytes.
Also note that the shortcut only appears on the SQL Prompt menu if you have a query windows opened. If you just connect SSMS to a server, the shortcuts doesn't work.
Is there any way to have a list of servers we don't want to use SQL Prompt, like some oldiers SP versions?
Regards, Ésio / comments
I disabled the SQL Prompt before connect to my SAP database.
Ok it isn't bringing any suggests, but it is still reading the schema for the database and consuming to many memory : 414MB for Ssms.exe...
Not good to know. I just migrate from version 3 to version 4.
I had a lot of servers/databases flags for ignore. It's specially important while connecting to SAP databases (about 87,000 tables/views). On my initial tests, query analyzer consumed about 800MB of ram.
Let's see how it will work after some days connecting/disconnecting from a farm os servers.
My vote to recover this feature for version 5.
Regards,
Ésio / comments
Not good to know. I just migrate from version 3 to version 4.
I had a lot of servers/databases flags for ignore. It's specially important while connecting to SAP databases (about 87,000 tables/view...