Comments
Sort by recent activity
Yes, you can add a SQL 'where' clause to each table, to filter the data you're synchronizing. You can configure this on the 'Tables & Views' tab.
See here for more info.
I hope this helps. / comments
Yes, you can add a SQL 'where' clause to each table, to filter the data you're synchronizing. You can configure this on the 'Tables & Views' tab.
See here for more info.
I hope this helps.
Thanks for your post.
Unfortunately, migrations doesn't support working across branches at the moment. Here is a brief explanation why.
It's looking more and more common that people need it to work between branches, so it's something that we need to find a way to support. The development team are currently looking into it, but I'm not sure when it will be available. / comments
Thanks for your post.
Unfortunately, migrations doesn't support working across branches at the moment. Here is a brief explanation why.
It's looking more and more common that people need it to work...
Can you let me know which uservoice suggestion you're referring to, and I'll chase it up? / comments
Can you let me know which uservoice suggestion you're referring to, and I'll chase it up?
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...