Comments
Sort by recent activity
I've spent some more time on this and determined that the error only occurs if I attempt to synchronize the target from with SQL Compare. If I generate a script and execute it in Management Studio, it runs fine. This clearly seems to be a bug in SQL Compare.
Thanks - Randy / comments
I've spent some more time on this and determined that the error only occurs if I attempt to synchronize the target from with SQL Compare. If I generate a script and execute it in Management Studio,...
The scenario you describe isn't really a DBPro of SQL Compare issue. If DBPro (or any process) attempts to check out a file that is already checked out, an error will occur from the source control system, unless multiple checkouts are turned on. If multiple checkouts are turned on and another user has modified the file, this is a source control merge issue.
Randy
David Atkinson wrote:
I see where you're coming from. We'll look into improving this going forward.
What does DBPro do when a file that it needs to check out is checked out or has been since modified by another user?
David Atkinson
Red Gate Software
/ comments
The scenario you describe isn't really a DBPro of SQL Compare issue. If DBPro (or any process) attempts to check out a file that is already checked out, an error will occur from the source control ...
David,
If I understand correctly, before I synchronize a database to my script files that are under source control, I need to check out all files that could be affected. Is this the case? If so, I view this as a huge shortfall. The whole point of managing script files is to facilitate source control. To expect developers to check out all script files before a compare is done simply isn't feasible.
Randy
David Atkinson wrote:
SQL Compare 6 doesn't interact with source control systems. It merely saves files in a format that can be bound to source control, but this is a step you must take using your source control client.
Some editors will let you check in/out files and folders from source control so this will work for you if you are modifying the SQL scripts offline. However if you are synching back from a live database to scripts on your hard disk, you will need to check these in to source control as a separate step.
David Atkinson
Red Gate Software
/ comments
David,
If I understand correctly, before I synchronize a database to my script files that are under source control, I need to check out all files that could be affected. Is this the case? If so, I ...
David,
What I would be expecting would be the same level of integration that Visual Studio DB Pro has. When I compare a database to a project, and I choose to update the project based on the comparison, DB Pro checks out all script files as necessary. We're a 10 developer team working with a schema containing 3500 objects. It's just not practical to expect each developer to check out all 3500 objects (files) when synchronizing to the script files. And, it would be far too time consuming to selectively check files out, especially if the number of files more than a dozen or so, which I think would happen frequently.
Randy
David Atkinson wrote:
Randy,
Going forward we definitely have plans to implement proper SCC integration, but for the initial v6.0 release, objects will need to be checked out manually.
You will be able to compare from scripts to a live DB without doing a check out. But when you synch from a live database to scripts, any object scripts that will be modified should be checked out.
Can you expand on precisely what sort of source control integration you are expecting in SQL Compare? At what stage of the process do you think it should check out the relevant object scripts?
Thanks for the feedback,
David Atkinson
Red Gate Software
/ comments
David,
What I would be expecting would be the same level of integration that Visual Studio DB Pro has. When I compare a database to a project, and I choose to update the project based on the compar...
Andras,
It appears that with v6, Red-Gate is moving towards a fuller database schema management suite of products (ala Microsoft's DBPro product). In order to do that schema validation is a requirement. It would be fantastic if v6 could issue warnings or errors as appropriate when scripts are the source or the target of a comparison.
Randy
Andras wrote:
randyminder@yahoo.com wrote:
Will v6 have any capability of detecting errors in scripts? For example, say I have a script that contains a Select statement and the table being selected from doesn't exist. Will v6 detect this and give a warning or error before a comparison is done?
Thanks - Randy
Hi Randy,
there will be a certain amount of error detection, for example if a clr assembly is referenced that does not exists, we will give an error. However, we do assume that the scripts are correct creations scripts that can be executed successfully on SQL Server. In the above situation we will not give you an error. Indeed, not even SQL Server will give you an error, only when you try to execute the stored procedure. Consistency and syntax checking is not the purpose of this product, but we will consider taking it this way in the future.
Kind regards,
Andras
/ comments
Andras,
It appears that with v6, Red-Gate is moving towards a fuller database schema management suite of products (ala Microsoft's DBPro product). In order to do that schema validation is a require...