Activity overview
Latest activity by MartinButcher
Thanks for the reply Bart
However as I am now out of my trial period for Prompt 3 I am in a catch 22 situation. I cant eval it again to see of it works OK with service pack 2 and I dont want to buy it untill I have trialed it and confirmed it works OK!! [image] / comments
Thanks for the reply Bart
However as I am now out of my trial period for Prompt 3 I am in a catch 22 situation. I cant eval it again to see of it works OK with service pack 2 and I dont want to buy...
2005 Service pack 2
I recently evaluated Prompt 3 when I had the pre-release version of sql 2005 service pack 2 installed and it created an entry in the Sql Manager Tool Bar but it was greyed out.
This was fixed with ...
I have the same problem.
If I highlight a block of text to do anything my machine hangs for about 30 seconds, If I turn of prompt its all OK.
I had service pack 2 installed by the way but deinstalled it.
But I stll had to run the pre-release version of prompt to get it to work at all on my PC.
At the moment I have turned it off as it is unworkable as it is.
I will revert to the freebe version I had before as this seems to work OK / comments
I have the same problem.
If I highlight a block of text to do anything my machine hangs for about 30 seconds, If I turn of prompt its all OK.
I had service pack 2 installed by the way but deinstall...
Hi Brian
It seems the problem has gone away! (Picture me red faced here)
I edited my sql compare project to use the database snapshots I had just generated in response to you request. (I usually just use the actual dbs) and everything worked OK so I re-edited the project to use the actual dbs and afer taking several minutes to register my live production db the sycronisation worked as I expected again.
Could it be that the project got corrupted in some way?
Martin / comments
Hi Brian
It seems the problem has gone away! (Picture me red faced here)
I edited my sql compare project to use the database snapshots I had just generated in response to you request. (I usually ju...
Hi Brian
Thanks for the reply.
I have tested this extensivly and even gone to the bother of naming my primary keys explicitly. It seems that every time a constraint other than the primary key or index is changed, then SQL Compare will try to drop the key constraints as well as the specific constarint on the non key field that has changed. It only does this on the tables that have had a constraint changed, it ignores key name changes on other tables that have not had a non key constraint change.
However if I apply this script then make another non key constarint change on one of the unaffected tables then the product will try to drop the keys on this table that it ignored the first time.
This leaves me with closely checking and editing the script by hand to remove the unwanted code which defeats the purpose of the product. / comments
Hi Brian
Thanks for the reply.
I have tested this extensivly and even gone to the bother of naming my primary keys explicitly. It seems that every time a constraint other than the primary key or in...
I think I have found a partial reason for my problem though the behavior of the product is still slightly illogical.
When you check the Constraint and Index Names Option a message comes up saying:
'Ignore the names of indexes, foreign keys, primary keys, and defualt, unique, and check constraints when comparing databases. Note the names will not be ignored when the databases are syncronised.'
This seems to be the root of the problem. They dont show up in the compare but do in the syncronization script. However the script is not acting as I would expect. If it is going to try to drop a key because it has a differing name surly it should try to re-create it with the new name?
And surely it should drop all keys with differing names not just the ones in tables that are having their constraints or binding changed? / comments
I think I have found a partial reason for my problem though the behavior of the product is still slightly illogical.
When you check the Constraint and Index Names Option a message comes up saying:
...
Hi Brian
The only reason I can see why it would want to drop the primary keys / indexes is that the names are different between the 2 versions of the database.
The example I gave you above of the workstation has nothing else done to it in the syncronisation script.
But even if the key gets dropped because of the name I would expect it to get rebuilt with the new name which didnt get included in the script.
By the way I am running SQL 2005 service pack 1
Key names
Development = PK__Workstation__605D434C
Production = PK__Workstation__3943762B / comments
Hi Brian
The only reason I can see why it would want to drop the primary keys / indexes is that the names are different between the 2 versions of the database.
The example I gave you above of the w...
I currently have the following options set
Indexes,
Constraint and Index Names
White Space
Comments
Users Permissions and role memberships
statistics
foreign keys
fill factor
filegroups
certificates
user properties
with element order / comments
I currently have the following options set
Indexes,
Constraint and Index Names
White Space
Comments
Users Permissions and role memberships
statistics
foreign keys
fill factor
filegroups
certificate...
Hi Brian
Tried your suggestion about setting ignore index and constraint names but it still wants to drop the primary keys. I also had ignore indexes set and it it tried to drop 3 indexes as well as the primary keys
By the way the create database script for the devolopment DB is created through Erwin Datamodeler which as you say auto names the constraints and keys / comments
Hi Brian
Tried your suggestion about setting ignore index and constraint names but it still wants to drop the primary keys. I also had ignore indexes set and it it tried to drop 3 indexes as well a...
Hi Brian
Some more info for you
This is the script generated for one of the tables. Notice it does not try to recreate the primary key. It also fails to delete the primary key as I have the 'Include dependancies' option turned off and it is being referenced by another table as a foreign key.
NB The primary key is on ClubID and WorkstationID
PRINT N'Dropping constraints from [dbo].[Workstation]'
GO
ALTER TABLE [dbo].[Workstation] DROP CONSTRAINT [CK__Workstati__Statu__375B2DB9]
GO
PRINT N'Dropping constraints from [dbo].[Workstation]'
GO
ALTER TABLE [dbo].[Workstation] DROP CONSTRAINT [CK__Workstati__TypeC__384F51F2]
GO
PRINT N'Dropping constraints from [dbo].[Workstation]'
GO
ALTER TABLE [dbo].[Workstation] DROP CONSTRAINT [PK__Workstation__3943762B]
GO
PRINT N'Adding constraints to [dbo].[Workstation]'
GO
ALTER TABLE [dbo].[Workstation] ADD CONSTRAINT [CK__Workstati__Statu__5E74FADA] CHECK (([Status]='IN' OR [Status]='AC'))
GO
ALTER TABLE [dbo].[Workstation] ADD CONSTRAINT [CK__Workstati__TypeC__5F691F13] CHECK (([TypeCode]='HO' OR [TypeCode]='PS')) / comments
Hi Brian
Some more info for you
This is the script generated for one of the tables. Notice it does not try to recreate the primary key. It also fails to delete the primary key as I have the 'Includ...