Red Gate forums: SQL Source Control 2 EAP

New Visual SourceSafe (VSS) Early Access version available

gyorgy.pocsi — Wed, 30 Mar 2011 18:11:41 GMT

New Visual SourceSafe Early Access version is now available to download:

https://www.surveymk.com/s/SqlSourceControl_EapSignup

Please note that this version supports VSS only. If you use other version control system please click on the following link:

http://www.red-gate.com/messageboard/viewforum.php?f=144

RE: Failed to locat CLR

laazyj — Tue, 22 Feb 2011 08:44:00 GMT

Thanks David. I hope you can implement it soon, as we won't be able to update our SQL Source Control installations until it is available.

RE: Failed to locat CLR

David Atkinson — Mon, 21 Feb 2011 17:15:34 GMT

Ah...

This may indeed cause problems, and it's because SQL Source Control isn't as advanced as SQL Data Compare right now.

We'll be implementing a feature to ignore schema objects soon. Following this, if there's enough demand, we'll consider doing the same for data columns.

David

RE: Failed to locat CLR

laazyj — Mon, 21 Feb 2011 16:28:10 GMT

Hi David,

The problem we have is that the current EAP builds of SQL Source Control aren't usable because of the limited data support.

We use the tools in the following way:
1. A single SVN repository
2. SQL Source Control for developers to check-in changes to this source tree.
3. Custom SQL Compare and SQL Data Compare scripts to deploy changes from the repository to our test, staging, production environments

Testing we've done with the pre-release SQL Source Control have failed because it always tries to overwrite the data in the repository.
We won't be able to use the new release unless either we can completely disable data support in SQL Source Control, or the data support is enhanced to allow us to specify which columns to source-control.

Is it possible to disable source controlling of data in the release candidate, even when data exists in the SVN repository?

Jason

RE: Failed to locat CLR

David Atkinson — Mon, 21 Feb 2011 14:35:20 GMT

The SQL Source Control release candidate due out very soon will have the SC-1350 fix.

Unfortunately, the ability to exclude columns in SQL Source Control will not be available in this version. If this is something that won't work for you, you will need to carry on using SQL Data Compare to push your static data as you are currently doing.

Kind regards,

David Atkinson
Red Gate Software

RE: Failed to locat CLR

laazyj — Mon, 21 Feb 2011 08:25:38 GMT

Thanks for the reply David. I can't use the current EAP builds, they don't play nicely with our SQL Data Compare scripts for managing static data.
We're patiently waiting for this feature request so we can use SQL Source Control for managing data as well.

Do you know if this will make it into the next official release?

RE: Failed to locat CLR

David Atkinson — Sun, 20 Feb 2011 19:41:55 GMT

Hi,

I've checked the SC-1350 issue in our bug tracking system and it looks like it might have been fixed. Have you checked the recently circulated early access build?

Kind regards,

David Atkinson
Product Manager
Red Gate Software

RE: Failed to locat CLR

laazyj — Sun, 20 Feb 2011 14:59:34 GMT

I'm having the same problem, introduced in the same way.
Database was working fine. Restored from a backup and now it fails with the "Failed to locate the CLR assembly..." exception even though the CLR assembly is properly installed, enabled and usable within a query.

RE: No indicator in SSMS when static data has changed

james.billings — Wed, 16 Feb 2011 14:28:00 GMT

Currently, you won't get the blue blobs for static data changes. You'll need to visit the commit tab, where it should show up.

We do have a job logged to implement this (ref. SOC-2047) although I'm not currently sure when it is likely to be implemented. If it's an important feature for you, you can suggest it on our uservoice forum here so other users can also vote for it.

RE: cannot Compare/Deploy data from source control?

David Atkinson — Tue, 15 Feb 2011 20:05:34 GMT

SQL Data Compare Pro can't yet deploy from SSMS in the same way as SQL Compare Pro does currently. This is because we haven't yet released SQL Source Control with data support except in early access, and therefore haven't yet implemented the integration.

To deploy currently you will need to "get" the scripts folder to a working folder on your hard disk, and simply use SQL Data Compare Pro on this.

David Atkinson
Red Gate Software

RE: cannot Compare/Deploy data from source control?

troyhunt — Tue, 15 Feb 2011 19:33:02 GMT

According to the features list, you'll need to go pro in order to compare against a folder of scripts from VCS: http://www.red-gate.com/products/sql-development/sql-data-compare/features

How to configure the polling interval to reduce server load

David Atkinson — Tue, 15 Feb 2011 17:13:47 GMT

If your server is struggling due to the default blue indicator polling frequency, it is possible to reconfigure it.

The settings are in milliseconds. If you set the interval to '0', it will turn off polling entirely, which means the blue indicators in the Object Explorer will only be set when the Commit tab is visited, but it should reduce the load on your database server.

All SQL Source Control users need to set this individually.

To achieve this you will need to edit the 'RedGate_SQLSourceControl_Engine_EngineOptions' in your SQL Source Control configuration directory. This is either: C:\Users\<username>\AppData\Local\Red Gate\SQL Source Control 1 or C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\SQL Source Control 1 depending on your operating system version.

The following XML is an example of setting the polling frequency to '0'. This will mean that SQL Source control will not check for changes until you visit the Commit tab. You might want to try different values between 0 and the defaults, until you have an acceptable performance.

Code:
<?xml version="1.0" encoding="utf-16" standalone="yes"?>
<EngineOptions version="2" type="EngineOptions">
<DefaultTraceMinimumInterQueryTimeInMillis>0</DefaultTraceMinimumInterQueryTimeInMillis>
<SysObjectsMinimumInterQueryTimeInMillis>0</SysObjectsMinimumInterQueryTimeInMillis>
<SysTypesMinimumInterQueryTimeInMillis>0</SysTypesMinimumInterQueryTimeInMillis>
<DefaultTraceMinimumRequestedInterQueryTimeInMillis>0</DefaultTraceMinimumRequestedInterQueryTimeInMillis>
</EngineOptions>

THE v1 DEFAULT VALUES ARE:
25000 DefaultTraceMinimumInterQueryTimeInMillis
2500 SysObjectsMinimumInterQueryTimeInMillis
3500 SysTypesMinimumInterQueryTimeInMillis
5000 DefaultTraceMinimumRequestedInterQueryTimeInMillis

cannot Compare/Deploy data from source control?

chattabaugh — Mon, 14 Feb 2011 22:09:51 GMT

Is there a way to compare data from a database to Source control?

When I go to Show History and pick a version that has data changes. I do not have the option to compare with DataCompare; only Compare Pro.

Same goes for If I right click on a database and select Data Compare/Deply I do not have the source control options that I have with Schema Compare/Deploy

v2.0 - now works with Vault (Pro), Mercurial, Perforce, GIT

gyorgy.pocsi — Tue, 08 Feb 2011 12:57:11 GMT

The new Early Access release of SQL Source Control 2.0 now supports the following version control systems:

Vault Standard 5.x
Vault Pro 5.x
Visual Source Safe 6.0d and 2005

Mercurial
Perforce
GIT
Bazaar
CVS

Your system not listed? If your version control system has a command line client interface you can set up SQL Source Control to work with it.

To try the new EA click on the following link:
https://www.surveymk.com/s/SqlSourceControl_EapSignup

Click here to learn more about the the new EA:
http://www.red-gate.com/supportcenter/Content?p=SQL%20Source%20Control&c=SQL_Source_Control/articles/release_notes_v2_0_1.htm

Please note that the history is not available from within SSMS when using Mercurial, Perforce, GIT, Bazaar and CVS.

RE: Option to go offline

Linda Hawksworth — Thu, 20 Jan 2011 11:52:10 GMT

Hi Claudio

I have sent you a PM requesting a screenshot.