Activity overview
Latest activity by guruper2
Thanks / comments
Thanks
The git command is the same for all my database projects and the comment i posted was "X". So that's not the issue here. The real problem is that the script being generated is wrong. All the files checked in to GIT is OK, but something special is happening to Node and Edge tables because they have "hidden" fields, and they are not scripted. Even though the $edge_id and $node_id fields are hidden in the table script, you can still put primary keys on them. The script should be: ALTER TABLE [Node].[Address] ADD CONSTRAINT [PK_Node_Address] PRIMARY KEY CLUSTERED ($node_id) ON [PRIMARY] But it shows as: ALTER TABLE [Node].[Address] ADD CONSTRAINT [PK_Node_Address] PRIMARY KEY CLUSTERED ON [PRIMARY] This causes all node and edge tables to show up having a difference, but the differences are not real. It's because the primary key is scripted wrong. / comments
The git command is the same for all my database projects and the comment i posted was "X". So that's not the issue here. The real problem is that the script being generated is wrong. All the files ...
The error is: Failed to execute git command 'commit --allow-empty-message -m x' I think the underlying issue is that there are no actual changes to check in. The local files are correct, but the UX comes up with "fake" changes when refreshing the commit window. / comments
The error is: Failed to execute git command 'commit --allow-empty-message -m x'I think the underlying issue is that there are no actual changes to check in. The local files are correct, but the UX ...
Bug related to Node/Edge tables?
After initial commit, I still get all Node and Edge tables in the database in the list of changes. The compare engine says it's a change in the Primary key. When trying to commit the change, I get ...
I find it strange that SQL Server 2016 is not fully supported 1 year after the RTM launch. You also state compatibility in the marketing material. It says: "What can I compare, synchronize, and deploy?" - "SQL Server 2005, 2008, 2012, 2014, 2016, SQL Azure, & SQL Server on Amazon RDS databases". Not completely true then if I can't choose all objects. Do you have a list of known unsupported features in SQL 2016? I just have to take this into account when I design my systems so I still can use SQL Compare. I've used the Red Gate Products since the early beginning, but this is the first time I'm stuck. / comments
I find it strange that SQL Server 2016 is not fully supported 1 year after the RTM launch. You also state compatibility in the marketing material. It says: "What can I compare, synchronize, and dep...
Native Compiled Functions not working?
I have several function native compiled functions in my SQL Server 2016 SP1 database. I get an error on all of them trying to sync between my database and source control system. The same goes for S...