May 21, 2025 at 11:24 pm
There is a tool for that (local, on-prem and remote)
May 21, 2025 at 11:34 pm
Sorry if this is duplicate (on my end it doesn't appear as though my first reply saved and I was trying to edit it to quote the message I was replying to) my guess is the link to Github Desktop was blocked so without further ado and no link but search term...
Rod, they could set up a central Git server, no cost at all, locally and then use that. It's going to be all command line driven (although I'm sure there's a Git gui somewhere), but they'd at least have a way to manage changes & such better than a file in the file system.
There is a tool for that... Github Desktop
May 22, 2025 at 1:15 am
Rod, they could set up a central Git server, no cost at all, locally and then use that. It's going to be all command line driven (although I'm sure there's a Git gui somewhere), but they'd at least have a way to manage changes & such better than a file in the file system.
I see your point, Grant. I hesitate because I saw what happened when we had TFS on-prem. My employer is so dead set against spending any money that when our version of TFS went out of support, and I told them about it, they did nothing about it for years. I suspect that if I got a GitHub Server in there, they would fall back to bad behavior and just let it continue. It's just another form of technical debt, which we have a LOT of.
OK, I admit that I'm probably being paranoid.
Rod
May 22, 2025 at 11:32 am
I see your point, Grant. I hesitate because I saw what happened when we had TFS on-prem. My employer is so dead set against spending any money that when our version of TFS went out of support, and I told them about it, they did nothing about it for years. I suspect that if I got a GitHub Server in there, they would fall back to bad behavior and just let it continue. It's just another form of technical debt, which we have a LOT of.
OK, I admit that I'm probably being paranoid.
Oh, you have reason to be paranoid. There's a small gap, until crossed, you don't see the utility of source control. It just takes education and a bit of experience, but then suddenly that gap gets crossed and there's no going back. However, the resistance to this, especially in traditional DBA circles, can be insanely difficult to overcome. But, education and a bit of experience and even the hardcore come around.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 22, 2025 at 12:11 pm
"It's a pull because you're asking someone to accept your code. You pushed it into the Pull Request, but they don't have to take it. They have to pull it."
Eh?! It kinda reminds me of that description of Cricket. "
You have two sides, one out in the field and one in. Each man that's in the side that's in goes out, and when he's out he comes in and the next man goes in until he's out. When they are all out, the side that's out comes in and the side thats been in goes out and tries to get those coming in, out. Sometimes you get men still in and not out.
When a man goes out to go in, the men who are out try to get him out, and when he is out he goes in and the next man in goes out and goes in. There are two men called umpires who stay all out all the time and they decide when the men who are in are out. When both sides have been in and all the men have out, and both sides have been out twice after all the men have been in, including those who are not out, that is the end of the game!"
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
May 22, 2025 at 12:12 pm
Duplicate post killed
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
May 22, 2025 at 12:32 pm
"It's a pull because you're asking someone to accept your code. You pushed it into the Pull Request, but they don't have to take it. They have to pull it."
Eh?! It kinda reminds me of that description of Cricket. "
You have two sides, one out in the field and one in. Each man that's in the side that's in goes out, and when he's out he comes in and the next man goes in until he's out. When they are all out, the side that's out comes in and the side thats been in goes out and tries to get those coming in, out. Sometimes you get men still in and not out.
When a man goes out to go in, the men who are out try to get him out, and when he is out he goes in and the next man in goes out and goes in. There are two men called umpires who stay all out all the time and they decide when the men who are in are out. When both sides have been in and all the men have out, and both sides have been out twice after all the men have been in, including those who are not out, that is the end of the game!"
Tracks.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 22, 2025 at 12:41 pm
"It's a pull because you're asking someone to accept your code. You pushed it into the Pull Request, but they don't have to take it. They have to pull it."
Eh?! It kinda reminds me of that description of Cricket. "
You have two sides, one out in the field and one in. Each man that's in the side that's in goes out, and when he's out he comes in and the next man goes in until he's out. When they are all out, the side that's out comes in and the side thats been in goes out and tries to get those coming in, out. Sometimes you get men still in and not out.
When a man goes out to go in, the men who are out try to get him out, and when he is out he goes in and the next man in goes out and goes in. There are two men called umpires who stay all out all the time and they decide when the men who are in are out. When both sides have been in and all the men have out, and both sides have been out twice after all the men have been in, including those who are not out, that is the end of the game!"
I haven't had enough coffee yet to even BEGIN to try to decipher what the heck is going on here...
LoL
May 22, 2025 at 3:14 pm
This is why I watch cricket with beer - it helps.
Well, not so much by the 5th day sometimes, maybe, but there you go.
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
May 22, 2025 at 7:09 pm
"It's a pull because you're asking someone to accept your code. You pushed it into the Pull Request, but they don't have to take it. They have to pull it."
Eh?! It kinda reminds me of that description of Cricket. "
You have two sides, one out in the field and one in. Each man that's in the side that's in goes out, and when he's out he comes in and the next man goes in until he's out. When they are all out, the side that's out comes in and the side thats been in goes out and tries to get those coming in, out. Sometimes you get men still in and not out.
When a man goes out to go in, the men who are out try to get him out, and when he is out he goes in and the next man in goes out and goes in. There are two men called umpires who stay all out all the time and they decide when the men who are in are out. When both sides have been in and all the men have out, and both sides have been out twice after all the men have been in, including those who are not out, that is the end of the game!"
May 22, 2025 at 8:31 pm
How do you control production deployments without source control? How can you be sure that the code that was tested is what gets deployed? In our world, nothing gets deployed to production without being in source control.
Without source control, how do you enforce naming standards? Or check for security holes? Or make sure that the deployed code is stored in a secure place and not on some random personal drive that gets deleted if someone leaves the company?
May 22, 2025 at 11:48 pm
How do you control production deployments without source control? How can you be sure that the code that was tested is what gets deployed? In our world, nothing gets deployed to production without being in source control.
Without source control, how do you enforce naming standards? Or check for security holes? Or make sure that the deployed code is stored in a secure place and not on some random personal drive that gets deleted if someone leaves the company?
Really simple rule: If it's not in source control, it doesn't exist.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 25, 2025 at 2:21 pm
Rod, what Grant said. Just make the folder the DBAs want to use a git repo. They can just keep dropping files. Then you can commit them 😉
I don't have access to the folder where the DBAs save their SQL scripts, so although that's a good idea, practically, I can't do anything about it.
Kindest Regards, Rod Connect with me on LinkedIn.
May 27, 2025 at 9:47 pm
How do you control production deployments without source control? How can you be sure that the code that was tested is what gets deployed? In our world, nothing gets deployed to production without being in source control.
Without source control, how do you enforce naming standards? Or check for security holes? Or make sure that the deployed code is stored in a secure place and not on some random personal drive that gets deleted if someone leaves the company?
Lots of organizations depend on someone like Grant to deploy things appropriately, and they don't worry about standards.
Viewing 14 posts - 16 through 29 (of 29 total)
You must be logged in to reply to this topic. Login to reply