Comments
Sort by recent activity
Good call on the Filters. I hadn't looked at those yet, and they seem to address my problems with the replication stored procedures and views.
To answer your other question:
I have an existing project that compares the scripts in the "C:\QDev\SQL Compare\Dev" directory to the live Production database.
After making some changes in the Development database, I want to re-script the database to the scripts folder to compare to Production.
If I choose "File > Export a Data Source" and point to the "C:\QDev\SQL Compare\Dev" folder, no files are overwritten. New files are created named "<objectname>1.sql".
I could script to another directory, but then I would have to modify the project before I can re-use it for comparison. That's why I would like to delete the existing scripts before exporting a Data Source.
David Atkinson wrote:
When you compare a data source to a scripts folder you should be able to generate a SQL Script OR change the files directly. The latter is the correct way to update your scripts folder. Is this not working for you?
Thanks for pointing that out. That does fix my problem! I had some trouble finding that option. It wasn't totally clear that I needed to choose "Synchronize using SQL Compare" in the Synchronization Wizard. Maybe you could add some help text or an explicit option "Synchronize Scripts Folder"?
I found a small bug in the Wizard. When you go from "step 2 - Review Dependencies" to "step 3 - Review Script", you can see the Affected files. If you go back to step 2 and go to step 3 again, the files will be in the list twice.
Thanks for the help! / comments
Good call on the Filters. I hadn't looked at those yet, and they seem to address my problems with the replication stored procedures and views.
To answer your other question:
I have an existing proj...
While not as easy as the automatic completion, you could write some code snippets.
I wrote one for "n", which inserts "N'$CURSOR$'", so in your case, I could just do "Field =" <SPACE> "n" <TAB>.
Same for LIKE, just write a snippet (maybe "li"?) to insert "LIKE N'%$CURSOR$%'".
To automate it, like you suggested, could be difficult. You could be writing a JOIN, and then you don't want the automatic ''. / comments
While not as easy as the automatic completion, you could write some code snippets.
I wrote one for "n", which inserts "N'$CURSOR$'", so in your case, I could just do "Field =" <SPACE> "n" <TAB>.
Sa...
Is this a feature request thread? I have a few...
:arrow: I like to write joins in the following way:
FROM <table1>
INNER JOIN <table2>
ON <table2>.<column> = <table1.column>
SQL Prompt only suggests "ON <table1>.<column> = <table2.column>"
Maybe you could add a join order preference?
:arrow: SQL Prompt doesn't look "up" more than one table
table1 has 2 foreign keys, to table2 and table3
SQL Prompt:
FROM <table1>
INNER JOIN <table2>
ON <table1>.<column> = <table2.column> --grr... see previous suggestion
INNER JOIN <table3>
ON ... Now it tries to find a matching column in table2, but *only* in table2, even though a real relationship exists with table1. / comments
Is this a feature request thread? I have a few...
:arrow: I like to write joins in the following way:
FROM <table1>
INNER JOIN <table2>
ON <table2>.<column> = <table1.column>
SQL Prompt only sugges...
Try this: SELECT *
FROM dbo.Test
-- this line will not be parsed
/* -- neither will this line
here ALL keywords are capitalized, AND the intellisense kicks IN example:
SELECT TOP 45 *
FROM dbo.Test
here nothing happens again */
The single line comments are handled correctly, and the lines with the start and end tag of the multi-line comment are ok too.
It's just the lines that do not have the multi-line markers that are a problem.
If the first select query (the one outside the comment) is removed, the intellisense won't kick in.
Hope this helps with finding the bug.
Kind regards and happy holidays,
Turambar / comments
Try this:SELECT *
FROM dbo.Test
-- this line will not be parsed
/* -- neither will this line
here ALL keywords are capitalized, AND the intellisense kicks IN example:
SELECT TOP 45 *
FROM dbo.Test...
I got the same error. It can be easily reproduced:
- Go to the snippet editor
- Do not select any snippet
- Click inside the textbox below "code for selected snippet:" / comments
I got the same error. It can be easily reproduced:
- Go to the snippet editor
- Do not select any snippet
- Click inside the textbox below "code for selected snippet:"
I use an @Error variable I set after almost every statement.
The following snippets keep me sane:
sete:
SET @Error;
and
ife:
IF(@Error = 0)
BEGIN
END;
some others I use frequently:
be:
BEGIN
END;
st4:
SELECT TOP 450 *
FROM dbo
I use this is for when I want to test a query, without retrieving the thousands of rows it would return normally.
Hope this is helpful to anyone. / comments
I use an @Error variable I set after almost every statement.
The following snippets keep me sane:
sete:
SET @Error;
and
ife:
IF(@Error = 0)
BEGIN
END;
some others I use frequently:
be:
BEGIN
END;
s...
Here is the whole message.
Steps to reproduce:
Start Query Analyzer
Start SQL Prompt
Ctrl+N in QA (New window)
Assertion Failed: Abort=Quit, Retry=Debug, Ignore=Continue
at _11.WndProc(Message& m)
at ControlNativeWindow.OnMessage(Message& m)
at ControlNativeWindow.WndProc(Message& m)
at NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Application.Run()
at _10._1()
at AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at AppDomain.ExecuteAssembly(String assemblyFile)
Abort Retry Ignore
Note: You don't have to install, just start the program
Note for HotAir: CTRL+Shift+Insert copies message text to the clipboard (no need to type it all out) / comments
Here is the whole message.
Steps to reproduce:
Start Query Analyzer
Start SQL Prompt
Ctrl+N in QA (New window)
Assertion Failed: Abort=Quit, Retry=Debug, Ignore=Continue
at _11.WndProc(Message& m)...
I would like to be able to ignore certain Databases / Servers.
I sometimes have to connect to servers via a slow connection, and retrieving the metadata for the large databases there takes quite a while.
A similar option is in SQL Prompt 2.0 (Databases to ignore on the Candidates tab)
Another option that I miss from version 2 is the auto-capitalization of keywords. I like tidy SQL, but I'm too lazy to press SHIFT.
Another small thing: tooltips on the icons in the popup window would be nice. Now I have to press on the icon to see what it means (snippets, star? (disabled for me), common objects, etc.)
There is currently no way to edit the snippets (that only go to "cuni" ?) or add custom ones. I take it this feature will be added? / comments
I would like to be able to ignore certain Databases / Servers.
I sometimes have to connect to servers via a slow connection, and retrieving the metadata for the large databases there takes quite a ...