Comments
Sort by recent activity
It is not credible that SQL Doc 5 fails where SQL Compare 13 succeeds. For SQL Compare 13; VIEW DEFINITION is the only minimum permission needed. Even including the following option to exclude trusted assemblies, a VIEW SERVER STATE error was generated when SQL Doc submitted a select query against the sys.trusted_assemblies DMV. Option uri="http://sqldoc/project/selections/sections/trustedassemblies/include/" value="False" Defect or proposed feature request: SQL Doc should determine whether VIEW SERVER STATE permissions exist; and modify its behavior to not issue any DMV query requiring that permission. Where appropriate, in place of the parts of the documentation (nodes) for which the privileged DMVs are needed, a message stating the item cannot be documented because the user does not have view server state permissions. Alternative: an option to avoid privileged DMVs should be part of the .sqldoc project file. The difference between this option and that above is how the behavior is determined (by querying for the existence of permissions, or by a project file option). / comments
It is not credible that SQL Doc 5 fails where SQL Compare 13 succeeds. For SQL Compare 13; VIEW DEFINITION is the only minimum permission needed.Even including the following option to exclude trust...
BTW, the DMV sys.trusted_assemblies was introduced in SQL 2017 (I believe); so SQL Doc 5 must already have a mechanism to select which DMVs to use; and what documentation to produce based on version. It is not too much of a leap to include consideration of permissions in controlling the behavior of SQL Doc. / comments
BTW, the DMV sys.trusted_assemblies was introduced in SQL 2017 (I believe); so SQL Doc 5 must already have a mechanism to select which DMVs to use; and what documentation to produce based on versio...
Jessica, Thanks for answering the question and confirming SQL Data Compare cannot write back to a source control repository. (Although it can write to a working folder which may be under source control.) The difference in Jonathan's scenario and mine are that I have no way to use filters, deciding what to deploy where, since it is data in the same table object (rather than objects in different schemas) that I want to control by environment. / comments
Jessica, Thanks for answering the question and confirming SQL Data Compare cannot write back to a source control repository. (Although it can write to a working folder which may be under source con...
Alex, Thanks for the reference. While similar the scenario was different. Regards, Bob Good / comments
Alex, Thanks for the reference. While similar the scenario was different. Regards, Bob Good
I have a similar problem that I suspect is due to the encoding of the script used to create the object in each of the databases. (As in ASCII vs UTF-16 vs UTF-8).
Try unchecking the ignore whitespace option in the comparison. Then re-compare to see what the differences are.
There is a post related to encoding that resulted in Bug Report reference SC-7653. / comments
I have a similar problem that I suspect is due to the encoding of the script used to create the object in each of the databases. (As in ASCII vs UTF-16 vs UTF-8).
Try unchecking the ignore whitespa...
How can I control the following behavior?
SQL Doc outputs the MS_Description extended property including nbsp in place of normal spaces.
This causes a very long horizontal scroll situation, including making the html output unprintable on a single page.
and example of the html source created is:
The name of the container of the report. Typically the name of the Access database, SQL database, SQL Report server, DTS container, Excel workbook, etc. where the report definition or code resides
The preferred output would be a wrappable and readable:
The name of the container of the report. Typically the name of the Access database, SQL database, SQL Report server, DTS container, Excel workbook, etc. where the report definition or code resides
Regards,
Bob Good / comments
How can I control the following behavior?
SQL Doc outputs the MS_Description extended property including nbsp in place of normal spaces.
This causes a very long horizontal scroll situation, includi...
Found the problem - wasn't the build (still failed after upgrade).
I should have documented following steps above.
Add change steps above to:
1a (add) Copy subversion branch to tagged branch for release.
6 and 7 used tagged branch to deploy from.
Problem: Migration script includes a separate meta file with .migrationScript extension that has URL (and revision number) to the database script repository.
I presume these are so SQL Compare can calculate the changes up to the migration script, then apply the migration script, and finally generate a script to bring the DB up to date. Essentially telling SQL Compare what the database should look like before and after the script.
I'm not sure there is a reliable work-around to this one. While I can (and did) change the URL in the .migrationScript to match the new branch. This resulted in SQL Compare showing the existance of the script and including the wizard step to include it in the deployment. However the specific revisions referred to do not exist in that branch. It is easy to think of some scenarios where the result may not be as intended.
So for the moment, deploying from a tagged or release branch using migration scripts is problematic.
David, I hope the reason you are available so late is that you are on the west coast preparing for SQL in the City Seattle. Caught your presentations in Chicago and I recommend them to anyone doing version control or deployment. / comments
Found the problem - wasn't the build (still failed after upgrade).
I should have documented following steps above.
Add change steps above to:
1a (add) Copy subversion branch to tagged branch for re...
Also, I now see similar information, confirming issues with branching, in the SQL Source Control 3 forum from last May 2012. / comments
Also, I now see similar information, confirming issues with branching, in the SQL Source Control 3 forum from last May 2012.
I'm using 10.2.0.1331.
I see that 10.2.3.1 is available. I will try it. / comments
I'm using 10.2.0.1331.
I see that 10.2.3.1 is available. I will try it.
I am also having a problem with SQL Compare detecting there is a scripts folder, unless launched from within SSMS using an actual database as the source (then changing it to source code).
Using SVN as repository and opening SQL Compare directly I haven't been able to detect the scripts folder. On migration wizard, migration scripts step is grayed out.
Steps to reproduce:
1. Have a database under source control, and at least one migration script checked into source control.
2. Open SQL Compare. (my version 10.2.0.1337)
3. Choose Source control as source.
4. Choose <Browse source control> in repository drop down.
5. Choose SVN
6. Paste or browse for Database Repository URL
7. Paste or browse for Migration Scripts Repository URL
8. Press [Link]
9. Select target database
10. Press Compare.
Expected result: Migration script symbol next to objects for which migration scripts were created. Step in wizard to select migration scripts to utilize.
Actual result: No migration script symbol for objects for which migration scripts were written. No step in wizard to select migration scripts to apply.
This behavior is different than if starting from SSMS, selecting a database to compare from initially, then switching to source control as the source.
In that case the symbol appears and the wizard step exists. / comments
I am also having a problem with SQL Compare detecting there is a scripts folder, unless launched from within SSMS using an actual database as the source (then changing it to source code).
Using SVN...