Comments
Sort by recent activity
SELECT length FROM string WHERE environment = 'unknown' As a basic rule try to keep it under 1000 rows. That said, obviously the number of cols, data types and number of other static data tables has a major effect too so (ahem) it depends. For a table with 10 cols and inexpensive data types you can probably stretch it quite a bit more than 1000 before hitting massive problems. I've seen customers get up to the 10s of thousands without too much hassle. At this point you might want to think about whether your source control system can handle files that big without falling over. For most people the issue they hit is maxing out the 2GB RAM limit in SSMS as SQL Source Control parses and scripts out the data in memory. However, you can also toggle the data comparison on and off if performance is an issue. Bottom line: give it a whirl and see. / comments
SELECT lengthFROM stringWHERE environment = 'unknown'As a basic rule try to keep it under 1000 rows. That said, obviously the number of cols, data types and number of other static data tables has a...
Ok, in that case I'm not sure. I'll bow out and hopefully someone else can answer you shortly. / comments
Ok, in that case I'm not sure. I'll bow out and hopefully someone else can answer you shortly.
You say you handle your deployments with Octopus Deploy - that's cool. But Octopus out of the box effectively just lets you deploy a NuGet package and run a script. Typically your script would execute some other process to run your deployment. Most of the folks on these forums will be using Octopus to orchestrate a task with Redgate SQL Change Automation, either from a PowerShell script or using one of the Redgate community step templates. If that's what you are doing, or if you are just running the SQL Compare command line, it should show up in SQL Monitor for you automatically. Is that what you are doing, or are you doing something else? / comments
You say you handle your deployments with Octopus Deploy - that's cool. But Octopus out of the box effectively just lets you deploy a NuGet package and run a script. Typically your script would exec...
Yep, I think that's how it works. /sourcecontrol is read inly but/scripts updates the files. But @Alex B can verify. Glad you got it working! / comments
Yep, I think that's how it works. /sourcecontrol is read inly but/scripts updates the files. But @Alex B can verify.Glad you got it working!
That's fair enough. Often "it depends". :-) Good luck with your implementation! / comments
That's fair enough. Often "it depends". :-)Good luck with your implementation!
In this scenario I would expect the files to be created on the filesystem, but not yet added to Git. Just to clarify, is it the case that: 1. The file exists on disk, but is not visible in Git (expected). 2. The file does not exist on disk or in Git (curious). Assuming scenario 1, open a command prompt and navigate to your git repo and run: > git status (It should show you have an untracked file.) Now run: > git add . (This will stage all changes ready to commit. If you wanted to cherry pick specific changes replace the . with the file names.) Finally: > git commit -m "your commit message here" Now the commit should show up in Git. (If you wanted to automate this task, following your schema compare, of course you could.) / comments
In this scenario I would expect the files to be created on the filesystem, but not yet added to Git.Just to clarify, is it the case that: 1. The file exists on disk, but is not visible in Git (expe...
@jschwarz_continuus: I'm afraid SQL Source Control does not have a PS/cli interface, but Git does. You could do what you want by running the SQL Compare command first, and then running a few git commands. However, it's not normally desirable to automate source control commits. Typically in a CI process, a developer will write their code, commit it carefully, and then the automated processes recognise the commit/push and run various builds, tests and deploys etc. / comments
@jschwarz_continuus: I'm afraid SQL Source Control does not have a PS/cli interface, but Git does. You could do what you want by running the SQL Compare command first, and then running a few git co...
It will just update the files. It won't do the commit. Also, SQL Source Control does a lot of clever stuff behind the scenes that SQL Compare won't do for you: https://documentation.red-gate.com/soc7/reference-information/how-sql-source-control-works-behind-the-scenes / comments
It will just update the files. It won't do the commit.Also, SQL Source Control does a lot of clever stuff behind the scenes that SQL Compare won't do for you:https://documentation.red-gate.com/soc7...
Sorry - I neglected to follow replies to this thread and just spotted your responses. Glad you got it figured out. Good luck! / comments
Sorry - I neglected to follow replies to this thread and just spotted your responses. Glad you got it figured out. Good luck!