Activity overview
Latest activity by davec
Do you have any recommendations on how to deal with replicated databases in source control in the mean time?
Should we have one database that isn't replicated and bind that to source control, and have another replicated database that isn't bound to source control. Than keep the unbound db up to date using SQL Compare...
Is that the best we can do for now? / comments
Do you have any recommendations on how to deal with replicated databases in source control in the mean time?
Should we have one database that isn't replicated and bind that to source control, and h...
But this issue is with SQL Source Control...
Am I missing something? / comments
But this issue is with SQL Source Control...
Am I missing something?
Hi David,
We are doing merge replication and the objects that are giving us grief are all the triggers, etc that include a GUID supplied by the server when replication is turned on.
i.e.
create trigger [MSmerge_del_6B0A0FF8ADDE416C9BF3853E8769F39A] on [server].[dbo].[tablename] FOR DELETE AS
declare @is_mergeagent bit, @at_publisher bit, @retcode smallint
Replication also adds constraints, indexes and statistics. These also need to be filtered out for a replicated database to be bound to source control when shared. / comments
Hi David,
We are doing merge replication and the objects that are giving us grief are all the triggers, etc that include a GUID supplied by the server when replication is turned on.
i.e.
create tri...
Hi,
We have a replicated database bound to source control and are running into a similar problem by not being able to exclude the replication elements that are created dynamically for each instance.
We have 3 different development sql servers in 3 different companies all using the same database schema through TFS and Redgate source control.
It's not going well at the moment.
Are there any tricks you can share for when you bind a replicated database to source control?
Thanks in advance. / comments
Hi,
We have a replicated database bound to source control and are running into a similar problem by not being able to exclude the replication elements that are created dynamically for each instance...
It may be simpler to work out what objects it wouldn't work with. Table modifications would be one.
I'm getting to the point where I need to get some tools for my team. Can you please tell me if this feature will be in the next release or not?
If not, then I'll go with ApexSQL as we intend to fill in the data dictionary within the schema and I don't feel like wrapping if exists... around all the extended property drops .
Cheers,
Dave / comments
It may be simpler to work out what objects it wouldn't work with. Table modifications would be one.
I'm getting to the point where I need to get some tools for my team. Can you please tell me if t...
I don't think that it could be used without issues on table modification, but on extended properties, stored procs, functions, etc, you could have an option to do the drop if exists, create without too much drama.
It's not going to solve everything, but would go a long way in eliminating the amount of manual scripting required to make a script re-runable.
And that's why we buy these tools.
There are many reasons why databases these scripts are run against may not be identical in nature (selective release of patches, hot fixes, etc), and these scripts need to cater for that in an elegant way. / comments
I don't think that it could be used without issues on table modification, but on extended properties, stored procs, functions, etc, you could have an option to do the drop if exists, create without...
The problem is only fixed by an existance check if you're doing a drop and create with the check being for the drop.
I'm currently working on building a data dictionary into the schema using extended properties. So that is my immediate need.
So I guess from your application point of view, the option only applies if you turn of "Modify" and do drop, creates.
Cheers,
Dave / comments
The problem is only fixed by an existance check if you're doing a drop and create with the check being for the drop.
I'm currently working on building a data dictionary into the schema using extend...
It seems that ApexSQL get it.
It's a feature in their product and may sway my organisation that way, which would be a pity because I've liked the Redgate toolbelt for a while now.
Cheers,
Dave / comments
It seems that ApexSQL get it.
It's a feature in their product and may sway my organisation that way, which would be a pity because I've liked the Redgate toolbelt for a while now.
Cheers,
Dave
I concur with fred.
I have a requirement to be able to re-run scripts without it failing.
The check for existence before the drop would solve this for me.
I have to provide deployment scripts to a large number of databases that are outside my control and require more fault tolerant scripts that allow for this sort of minor anomalies.
Cheers,
Dave / comments
I concur with fred.
I have a requirement to be able to re-run scripts without it failing.
The check for existence before the drop would solve this for me.
I have to provide deployment scripts to a ...