Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

log files

The log files at

C:\Users<user>\AppData\Local\Red Gate\Logs\SQL Source Control 3

can completely consume the free space on my C drive within a day. I have watched the files in this folder grow to 10gb in an afternoon.

How do I turn these off or set a size limit. I would also like to move them to a different location.

8 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Stuart Davis shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  Chris Smith responded  · 

SQL Source Control v3.0.5.7 has been released and should have resolved the excessive logging in the product.

To get this version, please run Check For Updates from the Help menu in SQL Source Control. This is a free upgrade for existing licensed v3 users and for users with a Support & Upgrades contract.

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • John Unger commented  ·   ·  Report

    Still broken in 3.0.13.4214 using subversion. Just recovered a crashed dev server with over 24GB of logs. Is there a way to turn this off now???!!!

  • John commented  ·   ·  Report

    Additionally, re the AV software config suggestion:

    Our enterprise centrally enforces the installation, configuration and use of MS System Center 2012 Endpoint Protection. It is not possible for an end-user to configure this AV software to exclude folder structures of their choice.

  • John commented  ·   ·  Report

    I have v3.0.13.4214 installed.

    On an SQL Server with 30 dbs linked to SQL SC, I can watch the log file grow ~30 KB every 3-4 seconds. This growth appears to be constant and consistent. I do not have to be actively using SQL SC for the growth to occur.

    The log growth stops if I close SSMS altogether. On restarting SSMS a new log file is created (~700 KB) and does not grow any further until I connect to a SQL Server. Simply connecting to a server (whether or not any of it's databases are linked to SC) causes the log file to grow ~25 KB per server connected.

    As I start to use SQL SC against a few databases, I see the log file grow, but the sustained, consistent growth is not observable until I have used SQL SC against 15 or more dbs. I believe the growth is present after only 1 db, but at a rate that cannot be easily observed.

    Since I have a large number of dbs linked to SQL SC, I have (per instructions from Red-Gate tech support) disabled auto-updating of the db status via the following settings in C:\Users\j<username>\AppData\Local\Red Gate\SQL Source Control 3\RedGate_SQLSourceControl_Engine_EngineOptions.xml

    <?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>

    This situation results in log files being created that consume ~500 MB of disk space per day.

  • AdminJames Billings (Admin, Redgate) commented  ·   ·  Report

    Hi Ted - one possibility is that we're seeing a file as being frequently changed when it isn't. One cause of this could be AV software, so could you try excluding our folder structure in your user profiles from AV scanning? (i.e. c:\users\<username>\appdata\local\red gate\SQL Source Control 3) - another possibility is if your profiles are hosted on a network server, although this is less common.

    If neither of the above help, please send a couple of example logs over to support@red-gate.com so we can see what they contain. In the meantime you can safely delete the files.

  • Ted Williamson commented  ·   ·  Report

    We are experiencing the same issues here at our office, one of our DB devs discovered his hard drive was full as a result of this.
    I guess my question would be, is there a config setting somewhere that we can change to stop this from happening? And if not can you make one so its easy to remedy if it every happens again?

  • Nathan Bedford commented  ·   ·  Report

    I have version 3.0.12.3695, and I have to clear my logs out daily or else I'll run out of space. 20GBs per day some days.

    If it was fixed in the 3.0.5.7 release, it's back again. Would love to see a fix.

  • Cornel commented  ·   ·  Report

    We are running 3.0.9.18 and Log folder is at 43GB and when drive ran out of space. Updating to a newer minor version now, hoping to resolve this issue.

  • Stephen Anslow commented  ·   ·  Report

    In addition, suggest that the SSCv3 installer NUKE all prior version Log folders e.g., SSCv2 and SSCv1, please...(or at least offer us the choice to have them nuked...) Had Stuart not posted, I'd have those two folders around for ever...

  • D. Taft commented  ·   ·  Report

    It would be really nice if someone from redgate could post an answer to this question. Real problem this morning when I could not log into my machine because C was toast.