Comments
9 comments
-
Hi,
Sorry about the problems you're having. Could you try removing/renaming your options file
C:\Documents and Settings\<user>\Local Settings\Application Data\Red Gate\SQL Prompt 3\EngineOptions.xml
We're thinking that maybe it got corrupted somehow (did you install the previous beta?)
Regards,
Tilman -
Sorry, tried that with exactly the same results.
Having renamed the file I restarted SQL Prompt saw a new file with the same name get created, tried the ignore function, but with no success.
It just looks like the file is not being saved correctly.
Can I edit it directly?
Alasdair. -
Yes, you can edit the file by hand.
As another experiment, could you remove the whole folder and then try again? This seemed to fix another problem with the snippets file.
Tilman
PS: did you see the develpment re: SQL Server 7 in this thread?
http://www.red-gate.com/messageboard/vi ... php?t=3821 -
No joy there either I'm afraid. Folder re-created, files re-created but no storage of the ignore information.
Yes, I did notice the activity on suport for SQL Server 7. I have already been in touch with Bart and am pleased to report a very speedy response from him.
Cheers,
Alasdair. -
I'm getting same problem.
I had deleted that file, and didn't worked too.
Ésio -
I do not know if this might cause this issue but my copy of SQL Prompt is not installed in the default directory.
Also, how do I edit the file by hand?
Alasdair. -
Hi,I do not know if this might cause this issue but my copy of SQL Prompt is not installed in the default directory.Also, how do I edit the file by hand?
Regards,
Tilman -
Problem is I don't have any snippets to compare it with. I'm trying to stop it trying to connect to some servers, but don't know the XML tags required.
Alasdair. -
Hi Alasdair,
Here is what it looks like.
<MetaDataCache>
...
<BlacklistedDatabases>
<BlacklistedDatabaseSet>
<Server>server</Server>
<IsCaseSensitive>False</IsCaseSensitive>
<IsWholeServerBlacklisted>False</IsWholeServerBlacklisted>
<Count>1</Count>
<Database>db</Database>
</BlacklistedDatabaseSet>
<BlacklistedDatabaseSet>
<Server>whole server</Server>
<IsCaseSensitive>False</IsCaseSensitive>
<IsWholeServerBlacklisted>True</IsWholeServerBlacklisted>
<Count>0</Count>
</BlacklistedDatabaseSet>
</BlacklistedDatabases>
...
</MetaDataCache>
There are 2 entries here, one blacklisting a whole server, the other blacklisting only a specific database
This needs to be added to the SQL Prompt Meta Data.cache file in the same directory as the snippets file.
Hope that helps.
Tilman
Add comment
Please sign in to leave a comment.
To attempt to replicate the problem try this
1. Have QA running and SQL Prompt enabled,
2. Open the SQL Prompt options dialog from the Options... menu item in the SQL Prompt menu,
3. Add a server to the list of those to ignore on the Connections tab,
4. Exit QA,
5. Restart QA.
6. Open the SQL Prompt options dialog from the Options... menu item in the SQL Prompt menu,
7. Go to the Connections tab. You will notice that your server to ignore has disappeared.
If you open a connection to the selected server between steps 3 and 4 you will see that SQL Prompt does not attempt to get any schemas. Exectly what I wanted. If you do it after step 7 the annoying error message comes back.
I am running Windows 2000 professional service pack 4, my database servers are all remote, and my QA version is 8.00.760.
Alasdair.