How can we help you today? How can we help you today?
Andrew P
Hey Kev, The devs have created bug number SC-9645 for that issue and are currently investigating. Do let us know if you have any additional questions in the meantime! Warmly, / comments
Hey Kev, The devs have created bug number SC-9645 for that issue and are currently investigating. Do let us know if you have any additional questions in the meantime! Warmly,
0 votes
Hey Ed, This was fixed in v12.2.2.4140 I recommend you upgrade to the latest Frequent Updates release and retest. Do let me know if you continue to have this issue afterwards! / comments
Hey Ed, This was fixed in v12.2.2.4140 I recommend you upgrade to the latest Frequent Updates release and retest. Do let me know if you continue to have this issue afterwards!
0 votes
Hey Imran, Git is a distributed Version Control system - so usually it will not work well with a Shared model. Think about it this way if everyone has different local copies of the repository, but they are all working on the same database - which one is going to be correct, the database or the repository? The database would be always right - but the repositories will be in different states - so someone could make a change to the database, then someone else could make that change to their local repo - so the history now attributes the change to the incorrect user. If everyone was making changes and committing them to their local repositories, they would all have different git histories with duplicate entries with different revision numbers - so your remote git history would be really odd and incorrect making it less meaningful. If you are even thinking of using Migration Scripts - they will not even remotely work with this type of a setup because they rely on changes to the database and changes to the repository being directly related. Ordering becomes very important So you can hack around this fundamental issue by using the Git command line hooks (like you have done) - but they do not give you the option to push or pull - nor will you be able to view the Git history from SQL Server Management Studio. If you must use Git - then you should be using the Dedicated model. If you must use the Shared model - then you should be using a Centralized Versioning System such as Subversion or TFS. Do let me know if you have any questions or issues with this! Warmly, / comments
Hey Imran, Git is a distributed Version Control system - so usually it will not work well with a Shared model. Think about it this way if everyone has different local copies of the repository, but ...
0 votes
Hey Scott, Thanks for contacting us! What type of version control system are you using (Git, SVN, TFS)? What version of SQL Source Control are you using? Thanks! / comments
Hey Scott, Thanks for contacting us! What type of version control system are you using (Git, SVN, TFS)? What version of SQL Source Control are you using? Thanks!
0 votes