Allow me to specify where to save the Working Bases (e.g., Disk/Drive D instead of C)
The WorkingBases are saved on disk C:\Documents and Settings...”.
To save disk space on C:\, we would like the Working Bases on the disque D:\ (we have databases with more than 5000 procs). Is there a setup somewehere ?
In SQL Source Control v3.3, you can now configure the location of your working bases. Information is at https://documentation.red-gate.com/display/SOC33/The+specified+path%2C+file+name%2C+or+both+are+too+long.
-
MH commented
The paths seem to have changed during the last versions. Now,
C:\Users\<username>\AppData\Local\Red Gate\
has data: 150 MB rising ... we also have roaming profiles and we try to avoid storing data on our C: drives, as they are rather small SSDs. We have big D: drives where we would like to have such data. How can we change the paths for SQL Source Control?
-
MH commented
I tried your link
but need an (additional!!!) login? Why don't you just post it here? I consider this a bug, so please post where to change these directories - thank you!
-
Adrian commented
We also have the need to set the working directory, but for a different reason. Some of our login-names start with $. Having a $ in the path is not allowed by SQL Source Control leading to a failure when trying to link the database.
-
Rob commented
It's not so much the space consumed in C:\Documents and Settings\<user> as it is being able to put this directory wherever I want. E.g. I may choose to put it inside C:\Documents and Settings\<user>\My Documents\Visual Studio 2010\Projects\<some project>\sql so I can commit both scripts and code together from Tortoise<repo of choice>.
-
Daniel Hautle commented
We have an issue with roaming profiles. Thus we require a way to save the Redgate Working Bases somewhere else than in the C:\Documents and Settings
-
Mel Padden commented
We would very much like to see this feature implemented. This causes issues when persisting our developers' individual profiles to network shares.
-
Mel Padden commented
We would very much like to see this feature implemented. This causes issues when persisting our developers' individual profiles to network shares.
-
Rob commented
-
Rob commented
-
M. Kaptein commented
We have a smaller database (1600+ procs and 500+ tables). This takes 24MB of data per database, however we maintain several versions of the system. In our environment we have roaming profiles, so we would very much like to see an option to place these files somewhere else.
-
Hello,
Could you give us some additional information?
How much space is being used by
C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\SQL Source Control 0Within that directory, how big is the Transients folder?
And, how big is the WorkingBases folder?Have you unlinked a lot of databases? If so, we currently don't remove the corresponding WorkingBases folder so there could be some leftover directories that could be deleted.
We're hoping to have this configurable in a future release. We'll look into a workaround for now, but any information you can provide would be extremely helpful.
Thank you!
-
bjuergen commented
Yes. I also would like to have this. Even if mupltiple developers work on the same database.