Comments
Sort by recent activity
Hi m,
I'm afraid that capability doesn't exist within SQL Source Control yet.
If you'd like to suggest we add it, it'd be great to make that request on our uservoice forum.
In particular, there is already a request to "Change remote branch to pull and push from with Git", which you may like to vote on. / comments
Hi m,
I'm afraid that capability doesn't exist within SQL Source Control yet.
If you'd like to suggest we add it, it'd be great to make that request on our uservoice forum.
In particular, there is ...
Hi Alex,
If you're not using the Object Locking feature, it may be worth turning it off completely. We recently had another customer with similar performance issues to yours, and this helped them.
To turn the feature off:
1. Close Management Studio.
2. Go to the SQL Source Control config files folder. By default, this is located at %localappdata%Red GateSQL Source Control 4
3. Open RedGate_SQLSourceControl_Engine_EngineOptions.xml in a text editor.
4. Below the EngineOptions version line, add:
<EnableObjectLocking>False</EnableObjectLocking>
The file is case sensitive. Don't change the capitalization of the text.
Ignoring any comments (indicated with <!->), the final file should look like this:
<EngineOptions version="3" type="EngineOptions">
<EnableObjectLocking>False</EnableObjectLocking>
</EngineOptions>
The example above doesn't include any extra lines you may have included. For example, you may have included additional lines to set up change logging.
5. Save and close the file, and reopen Management Studio.
I hope that helps! / comments
Hi Alex,
If you're not using the Object Locking feature, it may be worth turning it off completely. We recently had another customer with similar performance issues to yours, and this helped them.
...
Hi Alex,
I noticed a copy/paste error in the steps I put before, so they may have been misleading. Can I just confirm that you put the "EnableObjectLocking" setting to "False"?
If so, I'll see what other options we may have for you. / comments
Hi Alex,
I noticed a copy/paste error in the steps I put before, so they may have been misleading. Can I just confirm that you put the "EnableObjectLocking" setting to "False"?
If so, I'll see what...
Hi khuber,
You're spot on, this is because of using SSH.
I'm afraid that's not something we currently support in SQL Source Control, so you'll have to continue pushing using git bash.
If you'd like us to add support for SSH, please post a new suggestion on our Uservoice forum. / comments
Hi khuber,
You're spot on, this is because of using SSH.
I'm afraid that's not something we currently support in SQL Source Control, so you'll have to continue pushing using git bash.
If you'd like...
Hi Opus,
You certainly can - a number of comparison options can be changed on the Setup tab within SQL Source Control, including "Ignore Statistics".
Hopefully this documentation page will help: https://documentation.red-gate.com/disp ... on+options
If you're using an older version of SQL Source Control (earlier than 3.8.4) then you'll have to access those options in a slightly different way. / comments
Hi Opus,
You certainly can - a number of comparison options can be changed on the Setup tab within SQL Source Control, including "Ignore Statistics".
Hopefully this documentation page will help: ht...
Hi foobarred1,
It sounds like the Static Data feature may be useful for you. Here's a link to the documentation for that: https://documentation.red-gate.com/disp ... tatic+data
Is that helpful? / comments
Hi foobarred1,
It sounds like the Static Data feature may be useful for you. Here's a link to the documentation for that: https://documentation.red-gate.com/disp ... tatic+data
Is that helpful?
Would it be possible to set up a separate database for these objects, rather than using tempdb?
If that's an option, SQL Source Control can be configured to use that database (this will have to be done for each of your developers).
Instructions for how to set this up can be found here: http://documentation.red-gate.com/displ ... +databases / comments
Would it be possible to set up a separate database for these objects, rather than using tempdb?
If that's an option, SQL Source Control can be configured to use that database (this will have to be ...
Hi Tim,
I'm afraid we don't currently support the Team Explorer 2015 client, so you won't be able to connect with this in SQL Source Control.
We're looking into this at the moment, and hope to be able to offer support for Team Explorer 2015 in the very near future.
In the meantime, would it be possible for you to install Team Explorer 2014? / comments
Hi Tim,
I'm afraid we don't currently support the Team Explorer 2015 client, so you won't be able to connect with this in SQL Source Control.
We're looking into this at the moment, and hope to be a...
Hi freecell1, thanks for your post.
It seems that setting the compatibility level of a database doesn't change the database version that gets reported by SQL Server, just the behaviour of the database in question. Running
SELECT @@VERSION
on the database on your developers SQL 2014 instance should confirm this.
In your case, I suspect the database is identifying itself as database version 12, although it's compatible with database version 10.
One of our teams is currently working on improved identification of database versions & behaviour at the moment, which will hopefully yield a chance to report the compatibility level in the way you'd like.
That will be a little way off though, so I'm afraid I'd have to suggest you continue with your workaround for the time being.
If your developers commit frequently, it may be worthwhile trying to automate that fix-up step. Running a local script to update the RedGateDatabaseInfo.xml before commit could make it less of a pain, or you may be able to create an SVN pre-commit hook to reject commits with the wrong DatabaseVersion (therefore keeping your build safer). I think a pre-commit hook could automatically fix-up the DatabaseVersion for you, but that's not a recommended thing to do with SVN so I couldn't recommend it. / comments
Hi freecell1, thanks for your post.
It seems that setting the compatibility level of a database doesn't change the database version that gets reported by SQL Server, just the behaviour of the datab...
Hi Matt,
Thanks for your post.
This isn't a feature of SQL Source Control right now, but it should be in the very near future! / comments
Hi Matt,
Thanks for your post.
This isn't a feature of SQL Source Control right now, but it should be in the very near future!