That sounds awesome, are you going to share it?
Ed Elliott (6/30/2015)
That sounds awesome, are you going to share it?
Been thinking about it, but not yet.
I might stick it on github at some point, but it's not production ready yet.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
Alex Friedman (6/30/2015)
Hmm, Red Gate's DLM dashboard is indeed an interesting development -- but it's still in beta, and does not integrate with source control. It simply compares databases.I've actually been doing the same using Red Gate's SQL Compare and my own DDL triggers, but it's nice that there's a proper tool for it now.
They do list integration with source control in the future on their roadmap, so that will be interesting.
Alex- It's actually out of beta now. To get it, you can visit the check-for-updates feature in SQL Compare and it will appear as an option in the installer. It pairs well with SQL Compare or any deployment process as it not only fires alerts when schema changes happen, but it also maintains a comprehensive log of past deployments. It can be downloaded from its product page and is free to use.
How would you like it to integrate with source control? This is something the team is pondering and we're very open to ideas from the SQL Server community.
Good article. But even with source control, keep putting in those comments in the stored procedures.
If you are going to have trustworthy source control you should only deploy from source control. I can't overstate how important that is. Backfills never get kept up to date. That can be annoying, especially keeping track of multiple environments. But the payoff is repeatable stable deployments and always knowing the state of your systems. We use git and have automated and manual teamcity deployments triggered off of checkins. Generally we do automated deployments for "code" objects, but still trigger builds manually for schema and no trivial data updates.
Iwas Bornready (6/30/2015)
Good article. But even with source control, keep putting in those comments in the stored procedures.
Absolutely. I was just making that point yesterday that even with source control, having comments in the code (sp's, views, etc.) makes troubleshooting much easier sometimes.
cdesmarais 49673 (6/30/2015)
If you are going to have trustworthy source control you should only deploy from source control. I can't overstate how important that is. Backfills never get kept up to date. That can be annoying, especially keeping track of multiple environments. But the payoff is repeatable stable deployments and always knowing the state of your systems. We use git and have automated and manual teamcity deployments triggered off of checkins. Generally we do automated deployments for "code" objects, but still trigger builds manually for schema and no trivial data updates.
Beautiful!
icastellanos (6/30/2015)
Iwas Bornready (6/30/2015)
Good article. But even with source control, keep putting in those comments in the stored procedures.Absolutely. I was just making that point yesterday that even with source control, having comments in the code (sp's, views, etc.) makes troubleshooting much easier sometimes.
Some comments will help, other will be a plain distraction or even misleading. I know some people who only ever put comments in at the top, which isn't too useful when you have many screens of code to go through. I have also seen some of the comments that belong to an early version being changed so that the only way of seeing what the comments are is to go back into the history of the source control system. Too many examples of the comments being wrong to trust them.
Yet Another DBA (7/2/2015)
Too many examples of the comments being wrong to trust them.
This is so true, we have had years and years of bad or incorrect comments, lets try a new approach!
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply