Activity overview
Latest activity by Turambar
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...
Compare replicated tables
It would be nice if there was an option to ignore replication objects. Our Development database is not replicated, but the Production one is. When I compare the two (Scripts Folder to Database), th...
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...
Unhandled exception in bracketedSubclause()
I get an exception while entering some code in Management Studio.
The following (syntactically incorrect) line of code will cause the error:
IF (@Error = 0) AND (COALESCE((@Tes...
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...
Suggestion: Complete should eat rest of word
Hi there.
I've been using the new beta of SQL Prompt today, and I must say that it is a great step forward from the previous beta (and version 2)
I have one suggestion, though.
I would like the com...
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...
CandidateList stealing application focus
This is a minor issue, but annoying nonetheless.
I have a Query Analyzer (QA) open and an explorer window containing a folder filled with SQL scripts.
Without SQL Prompt, when I drag a script from ...