Comments
Sort by recent activity
Sorry, I've been on holiday and missed your reply.
The easiest way to check the encoding is to save the file to disk, and then open it in notepad++. You can then find the encoding through the 'encoding' menu item. / comments
Sorry, I've been on holiday and missed your reply.
The easiest way to check the encoding is to save the file to disk, and then open it in notepad++. You can then find the encoding through the 'enco...
Sorry for the delay, I was on holiday last week.
I seem to get almost the opposite of what you're finding in point 3. With your script, I only stop getting suggestions when I set the value to below 7100, which is nowhere near the original declaration based on 1 byte per character. You seem to need to set nearly 4 bytes per character on your system.
There might be some significant differences in our systems, but I would think it should still be more consistent.
I'd like to see if I can replicate the problem you're having, so could you tell me:
1) Your OS and service packs
2) Exact version of SSMS
3) The encoding of a .SQL file when you save a script in SSMS.
For your reference, I've logged this issue as bug SP-4394. / comments
Sorry for the delay, I was on holiday last week.
I seem to get almost the opposite of what you're finding in point 3. With your script, I only stop getting suggestions when I set the value to below...
Thanks for your post.
I've haven't been able to reproduce this in a test case, so would you be able to post an example that reproduces this?
I've tried the following, which prompted me for @Meter at the <cursor> DECLARE @Meter TABLE (id INT, text VARCHAR(30))
DECLARE @Upper int;
DECLARE @Lower int
SET @Lower = 1
SET @Upper = 999
INSERT INTO @Meter (id) SELECT Round(((@Upper - @Lower -1) * Rand() + @Lower), 0)
IF (select TOP 1 id from @Meter) > 500
BEGIN
DECLARE @Delete TABLE (text VARCHAR(30))
INSERT INTO @Delete (text) SELECT 'Im Deleting stuff'
SELECT * FROM @Delete AS D
SELECT * FROM <cursor>
END
IF (select TOP 1 id from @Meter) <= 500
BEGIN
UPDATE @Meter SET text = 'Im not deleting stuff'
SELECT * FROM @Meter
END
/ comments
Thanks for your post.
I've haven't been able to reproduce this in a test case, so would you be able to post an example that reproduces this?
I've tried the following, which prompted me for @Meter a...
Sorry for the delay.
This is being considered a bug, so we should hopefully address it in a future release.
For your reference the bug tracking code for this is SP-3019. / comments
Sorry for the delay.
This is being considered a bug, so we should hopefully address it in a future release.
For your reference the bug tracking code for this is SP-3019.
Thanks for your post.
I can reproduce this here, so I can confirm that formatting the FETCH statement is something that SQL Prompt doesn't do.
I need to find out if the FETCH statements are supposed to be formatted (bug), or if it's something we need to add support for (feature).
I'll update this post when I find out. / comments
Thanks for your post.
I can reproduce this here, so I can confirm that formatting the FETCH statement is something that SQL Prompt doesn't do.
I need to find out if the FETCH statements are suppose...
Thanks for your post.
I've tested this out with v5.2.6.1 in SSMS 2008 R2 and didn't get the same behaviour.
I have native intellisense enabled as well.
What version of SSMS are you using? / comments
Thanks for your post.
I've tested this out with v5.2.6.1 in SSMS 2008 R2 and didn't get the same behaviour.
I have native intellisense enabled as well.
What version of SSMS are you using?
Thanks for your post.
I'm not sure what the plans are for adding configurable SDC options in SQL Source Control, but I'll check.
What was the discrepancy that SQL Data Compare highlighted?
Could it be caused by using a case sensitive collation, or having a different collation between the table script in source control, and the live database? / comments
Thanks for your post.
I'm not sure what the plans are for adding configurable SDC options in SQL Source Control, but I'll check.
What was the discrepancy that SQL Data Compare highlighted?
Could it...
Sorry for the delay.
The good news is that we're going to add SQL Data Compare options to SQL Source Control in a future version, but I'm not sure exactly when that will be.
The reason that a binary comparison isn't the default is mainly because it will force a case sensitive comparison, which isn't ideal if you're using a case insensitive collation. It will also mean that the collation rules are also ignored.
However, a binary comparison does work better with non-unique indexes. / comments
Sorry for the delay.
The good news is that we're going to add SQL Data Compare options to SQL Source Control in a future version, but I'm not sure exactly when that will be.
The reason that a binar...
Thanks for your post.
Could you try turning on the command line logging? It might give a better idea where the problem is:
/logLevel:<logLevel>
Alias: /log
Default: None
Sets a minumum log level
Log files collect information about the application while you are using it. These files are useful to us if you have encountered a problem. By default, logging is disabled and no log files are stored.
Value Alias Description
None n Disables logging.
Error e Reports serious and fatal errors. For example, an error message might report a failed operation.
Warning w Reports warning and error messages. For example, a warning message might report a handled exception, or a problem which does not prevent you from using the application.
Verbose v Reports all messages in the log file.
The logs are normally created in '%USERPROFILE%\AppData\Local\Red Gate\Logs\SQL Compare' / comments
Thanks for your post.
Could you try turning on the command line logging? It might give a better idea where the problem is:
/logLevel:<logLevel>
Alias: /log
Default: None
Sets a minumum log level
L...
Thanks for your post.
It looks like the error is coming from the SQL Compare engine parsing one of your objects.
Could you try comparing the schemas using SQL Compare? It should give you a better error if it encounters errors reading the objects.
If it shows you which object it's having trouble with, could you post or email me the SQL for that object?
There might be a bug in the engine parsing some of the syntax you're using. / comments
Thanks for your post.
It looks like the error is coming from the SQL Compare engine parsing one of your objects.
Could you try comparing the schemas using SQL Compare? It should give you a better e...