Quantcast
Channel: Open DBDiff
Viewing all 281 articles
Browse latest View live
↧

Commented Issue: Password with some characters generate strange error [15451]

March 12, 2015, 7:38 am
$
0
0
Hi guys,

First of all, let me thank you for this great peace of software.

One caveat:
When entering a password like '4J;%Y2|L', because of special characters, we get the following error message:

"Test failed! Format of the initialization string does not conform to specification starting at index 100."

I think the error message should be more specific.

Best regards,

Bruno Martins
Comments: Thanks for creating an account to report this issue. The Test button just puts the SqlException.Message right in the dialog. I'm not sure what we can do better (perhaps a special case for this error explaining common causes?) since there are so many different possible errors. This specific error apparently occurs because of the semicolon (';') in the password. It will be interesting trying to bullet-proof against all the potential characters that need to be escaped!
↧
Search

Edited Feature: FEATURE REQUEST: Add some Visual Differences function [15445]

March 12, 2015, 8:00 am
$
0
0
I have tweaked the code to provide a prototype Visual Comparison without having to add other components..

What I did...

1 - Split the New Object and Old Object tabs so that they are both always visual.
2 - Add two textboxes just below the New Object/Old Object. One is the "New Line" and the other is the "Old Line".
3 - Add an HScrollBar below the Old/New Line textboxes
4 - Adjust New/Old Objects to determine which line the caret is at and then pull that line from both New and Old Objects and drop just the line into the New/Old Line textboxes.
5 - Adjust the New scrollbars so they track each other.
6 - Adjust HScrollBar to scroll New/Old Line Textboxes together.

Then I did a few "extras"...

1 - If the lines are identical, leave New/Old Line textbox background as white. If they are different, make them Light Pink. If they are different, but only due to white space, make the background color yellow.
2 - Adjusted width of buttons and width of Schema Tree to give more space to the New Object and Old Object controls.

I did not take the step of trying to detect and color code individual lines, but that would be a nice feature. I also have not attempted to adjust the output so that each side is visually "Synced" I also did not attempt to add any sort of Next Difference or Previous Difference buttons. Each of these would be nice.
↧
↧

Commented Feature: FEATURE REQUEST: Add some Visual Differences function [15445]

March 12, 2015, 8:00 am
$
0
0
I have tweaked the code to provide a prototype Visual Comparison without having to add other components..

What I did...

1 - Split the New Object and Old Object tabs so that they are both always visual.
2 - Add two textboxes just below the New Object/Old Object. One is the "New Line" and the other is the "Old Line".
3 - Add an HScrollBar below the Old/New Line textboxes
4 - Adjust New/Old Objects to determine which line the caret is at and then pull that line from both New and Old Objects and drop just the line into the New/Old Line textboxes.
5 - Adjust the New scrollbars so they track each other.
6 - Adjust HScrollBar to scroll New/Old Line Textboxes together.

Then I did a few "extras"...

1 - If the lines are identical, leave New/Old Line textbox background as white. If they are different, make them Light Pink. If they are different, but only due to white space, make the background color yellow.
2 - Adjusted width of buttons and width of Schema Tree to give more space to the New Object and Old Object controls.

I did not take the step of trying to detect and color code individual lines, but that would be a nice feature. I also have not attempted to adjust the output so that each side is visually "Synced" I also did not attempt to add any sort of Next Difference or Previous Difference buttons. Each of these would be nice.
Comments: This functionality was as a part of pull request [8082](https://opendbiff.codeplex.com/SourceControl/network/forks/jbanderson99/visualenhancements/contribution/8082), but was left out in the initial merge (issue [#15458](https://opendbiff.codeplex.com/workitem/15458)). The previous pull request implemented the visual difference functionality using the [DiffPlex](https://github.com/mmanela/diffplex) project. I believe I will leave this as 'Resolved' but not closed since this implementation may be incorporated as an alternative differencing method, particularly if DiffPlex causes problems porting to another platform someday.
↧

Edited Feature: FEATURE REQUEST: Several TreeView upgrades [15444]

March 12, 2015, 8:03 am
$
0
0
It would be very helpful to have a couple of upgrades to the Tree View (Schema Tree View)...

1 - Show the number of non-identical items in each folder.

For example, if there are 10 tables and in the DB and 3 are different, the Tables folder would show "Tables (3/10)"

2 - Use alternate color on items that are different due only to white space.

For examples, if the a stored procedure if the same, except that there is an extra carriage return, that stored procedure would be colored Yellow (or Dark Goldenrod).
↧

Commented Feature: FEATURE REQUEST: Several TreeView upgrades [15444]

March 12, 2015, 8:03 am
$
0
0
It would be very helpful to have a couple of upgrades to the Tree View (Schema Tree View)...

1 - Show the number of non-identical items in each folder.

For example, if there are 10 tables and in the DB and 3 are different, the Tables folder would show "Tables (3/10)"

2 - Use alternate color on items that are different due only to white space.

For examples, if the a stored procedure if the same, except that there is an extra carriage return, that stored procedure would be colored Yellow (or Dark Goldenrod).
Comments: I didn't realize this issue already existed when I created [issue #15458](https://opendbiff.codeplex.com/workitem/15458); it appears that pull request covered these suggestions - thanks!
↧
↧

Edited Issue: NullReferenceException locating index parent ActionMessage [15442]

March 12, 2015, 8:13 am
$
0
0
Open DBDiff Beta 0.9.0.0
Error Generating Synchronized Script
NullReferenceException: Object reference not set to an instance of an object.
at DBDiff.Schema.SQLServer.Generates.Model.Index.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Index.cs:line 271
at DBDiff.Schema.Model.SchemaList'2.<>c__DisplayClass9.<ToSqlDiff>b__6(T item) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 126
at DBDiff.Schema.SQLServer.Generates.Model.Table.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Table.cs:line 371
at DBDiff.Schema.Model.SchemaList'2.<>c__DisplayClass9.<ToSqlDiff>b__6(T item) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.SQLServer.Generates.Model.Database.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Database.cs:line 249
at DBDiff.Front.Form1.ProcesarSQL2005() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff\Front\PrincipalForm.cs:line 125

651FC38BF0129E3705DB2A616E1FE770

See also: [#15406](https://opendbiff.codeplex.com/workitem/15406) NullReferenceException loading index parent
↧

Commented Issue: NullReferenceException locating index parent ActionMessage [15442]

March 12, 2015, 8:13 am
$
0
0
Open DBDiff Beta 0.9.0.0
Error Generating Synchronized Script
NullReferenceException: Object reference not set to an instance of an object.
at DBDiff.Schema.SQLServer.Generates.Model.Index.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Index.cs:line 271
at DBDiff.Schema.Model.SchemaList'2.<>c__DisplayClass9.<ToSqlDiff>b__6(T item) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 126
at DBDiff.Schema.SQLServer.Generates.Model.Table.ToSqlDiff() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Table.cs:line 371
at DBDiff.Schema.Model.SchemaList'2.<>c__DisplayClass9.<ToSqlDiff>b__6(T item) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.Model.SchemaList'2.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema\Model\SchemaList.cs:line 131
at DBDiff.Schema.SQLServer.Generates.Model.Database.ToSqlDiff(List'1 schemas) in c:\Users\JS\Desktop\Files\opendbiff\DBDiff.Schema.SQLServer2005\Model\Database.cs:line 249
at DBDiff.Front.Form1.ProcesarSQL2005() in c:\Users\JS\Desktop\Files\opendbiff\DBDiff\Front\PrincipalForm.cs:line 125

651FC38BF0129E3705DB2A616E1FE770

See also: [#15406](https://opendbiff.codeplex.com/workitem/15406) NullReferenceException loading index parent
Comments: Thank you both for reporting this issue.
↧

Reviewed: Open DBDiff 0.9 (Mar 12, 2015)

March 12, 2015, 12:33 pm
$
0
0
Rated 5 Stars (out of 5) - Works like a charm.
↧
Search

Updated Wiki: Contributing

March 13, 2015, 8:55 am
$
0
0

The official way to share your changes is to fork the project and create a pull request once your changes are committed to your fork. CodePlex documents this processhere; there are blog posts with additional details like this one here, though most tend to focus on github. If you've already made changes and you're not a fan of a manual merge you can try copying everything from where you've made your change over the top of the initial download from the fork and running the diff to see how things work out (hope that makes sense!).

Now that Visual Studio 2013 Community Edition is free and includes git support it is easy to recommend that as the best option. (Alternatives like Xamarin Studio are still working through some issues sharing project files and such.) If you have Visual Studio 2012 you can try the Visual Studio Tools for Git extension, but I don't have any experience with it. If you are comfortable with the command line and a bit of advanced setup, git has adecent installer.

In the past CodePlex allowed larger uploads related to issues but I can't find any way to attach anything larger than 4mb anymore. If necessary, I'm willing to do the merge for you if you .ZIP things up and email a link or the whole thing to me at OpenDBDiff @ gmail.com. If you're familiar with the diff/patch format(s) you're welcome to send just that to me - basically I'll do what I can to work with whatever you have.

Thanks for willingness to share your fixes; be sure to check out the other open source alternatives listed in the documentation in case any of them can save you some additional work! The policy here is to add anyone who has contributed a fix as a developer on the project.

Any feedback on ways to improve this process would be greatly appreciated... my goal is to remove anything preventing people from sharing their fixes and enhancements!

↧
↧

New Post: Newbie question: how do I submit a change?

March 13, 2015, 9:02 am
$
0
0
Thanks for creating an account to report this issue, and volunteering to share your fix!

See the general recommendations for contributing currently well hidden as a work in progress on the project wiki.
↧

Updated Wiki: Contributions Welcome

March 13, 2015, 9:07 am
$
0
0
The policy here is to add anyone who has contributed a fix as a developer on the project.

The official way to share your changes is to fork the project and create a pull request once your changes are published to your fork. Codeplex documents this process here; there are blog posts with additional details like this one here, though most tend to focus on github.

My personal preference for this project would be for you to create an issue documenting the problem you've found (you can do some searching to see if the issue already exists to save me some time) and indicate that you are working on a fix. This will hopefully keep others from duplicating your efforts. Then, you can reference the work item number in your commit message(s) prefixed with a '#' and CodePlex will link things up. Please commit often, separating code-clean-up related changes from actual fixes to make it easier to see what's going on.

If you're not a fan of a manual merge of changes you've already made I would try copying the changes you made directly overwriting the initial download from the fork and running the diff to see how things work out (hope that makes sense!).

The free Visual Studio Community edition includes support for git. If you have Visual Studio 2012 you can try the Visual Studio Tools for Git extension, but I don't have any experience with it. If you are comfortable with the command line and a bit of advanced setup, git has a decent installer.

In the past CodePlex allowed larger uploads related to issues but I can't find any way to attach anything larger than 4mb anymore. If necessary, I'm willing to do the merge for you if you .ZIP things up and email a link or the whole thing to me at OpenDBDiff @ gmail.com. If you're familiar with a diff you're welcome to send just that to me - basically I'll do what I can to work with whatever you have.

Thanks for willingness to share your fixes; be sure to check out the other open source alternatives listed in the Documentation in case any of them can save you some additional work!
↧

Updated Wiki: Contributions Welcome

March 13, 2015, 9:08 am
$
0
0
The policy here is to add anyone who has contributed a fix as a developer on the project.

The official way to share your changes is to fork the project and create a pull request once your changes are published to your fork. Codeplex documents this process here; there are blog posts with additional details like this one here, though most tend to focus on github.

Please consider creating an issue documenting the problem you've found (you can do some searching to see if the issue already exists to save me some time) and indicate that you are working on a fix. This will hopefully keep others from duplicating your efforts. Then, you can reference the work item number in your commit message(s) prefixed with a '#' and CodePlex will link things up. Please commit often, separating code-clean-up related changes from actual fixes to make it easier to see what's going on.

If you're not a fan of a manual merge of changes you've already made I would try copying the changes you made directly overwriting the initial download from the fork and running the diff to see how things work out (hope that makes sense!).

The free Visual Studio Community edition includes support for git. If you have Visual Studio 2012 you can try the Visual Studio Tools for Git extension, but I don't have any experience with it. If you are comfortable with the command line and a bit of advanced setup, git has a decent installer.

In the past CodePlex allowed larger uploads related to issues but I can't find any way to attach anything larger than 4mb anymore. If necessary, I'm willing to do the merge for you if you .ZIP things up and email a link or the whole thing to me at OpenDBDiff @ gmail.com. If you're familiar with a diff you're welcome to send just that to me - basically I'll do what I can to work with whatever you have.

Thanks for willingness to share your fixes; be sure to check out the other open source alternatives listed in the Documentation in case any of them can save you some additional work!
↧

Updated Wiki: Contributions Welcome

March 13, 2015, 9:09 am
$
0
0
The policy here is to add anyone who has contributed a fix as a developer on the project.

The official way to share your changes is to fork the project and create a pull request once your changes are published to your fork. Codeplex documents this process here; there are blog posts with additional details like this one here, though most tend to focus on github.

Please consider creating an issue documenting the problem you've found (you can do some searching to see if the issue already exists to save me some time) and indicate that you are working on a fix. This will hopefully keep others from duplicating your efforts. Then, you can reference the work item number in your commit message(s) prefixed with a '#' and CodePlex will link things up. Please commit often, separating code-clean-up related changes from actual fixes to make it easier to see what's going on.

If you're not a fan of a manual merge of changes you've already made I would try copying the changes you made directly overwriting the initial download from the fork and running the diff to see how things work out (hope that makes sense!).

The free Visual Studio Community edition includes support for git. If you have Visual Studio 2012 you can try the Visual Studio Tools for Git extension, but I don't have any experience with it. If you are comfortable with the command line and a bit of advanced setup, git has a decent installer.

In the past CodePlex allowed larger uploads related to issues but I can't find any way to attach anything larger than 4mb anymore. If necessary, I'm willing to do the merge for you if you .ZIP things up and email a link or the whole thing to me at OpenDBDiff @ gmail.com. If you're familiar with the diff/patch format(s) you're welcome to send just that to me - basically I'll do what I can to work with whatever you have.

Thanks for willingness to share your fixes; be sure to check out the other open source alternatives listed in the Documentation in case any of them can save you some additional work!
↧
↧

New Post: Error running script database, a database to another in SQL Server 2012

March 16, 2015, 5:18 am
$
0
0
Hi guys.

My problem is this, I have two databases on two different servers in SQL Server 2012 the two, and I'm using indexed views, functions that call that indexed views, full-text catalogs ...

I need to have the same structure in both, I want to change the database 1 and have the changes in the second without creating everything from scratch. I have tried using scripts and tools like db comparer and this tool. And in all the tools that I have used, the error is the same.

You can not use the CONTAINS or FREETEXT predicate in the indexed view 'dbo.vwProducts', because it is not indexed.

When I create the script, I select the option to create "full-text catalog", but definitely not create a catalog full text correctly. Is there any option to create a script data respecting the database 2 and also to incorporate "full-text catalog" and other changes? What about full-text catalogs, you can not take another database and put them in another? I do not want to do a full backup, because it would lose the data, would as far as possible, respecting the data and to make structural changes, such as creating a new column, some relationship FK new, etc ...

It is possible to do this with this tool?

Thank you very much in advance. If I give a way I'll let you know.
↧

New Post: Error running script database, a database to another in SQL Server 2012

March 16, 2015, 10:15 pm
$
0
0
This post on StackOverflow contains all the relevant troubleshooting info.

If you've verified that everything is setup correctly on the second server, it is possible that the generated script is broken. You would have to find the relevant portions to verify manually that the normal index is created properly prior to the attempt to create the full-text catalog failing.
↧
Search

Reviewed: Open DBDiff 0.9 (Mar 29, 2015)

March 29, 2015, 10:29 pm
$
0
0
Rated 5 Stars (out of 5) - Thank you for this very useful application :)
↧

Commented Issue: SQL2014 compare against SQL2008 - statistics index compare bug [15456]

April 17, 2015, 2:58 am
$
0
0
It seems that there is a bug in DBDiff tool when comparing two databases that are on different sql versions. In my case we have compared two identical DB on different sql versions - sql2008 vs sql2014. DBDiff tool reported difference in statistics indexes although statistics indexes were present in both DBs.
Comments: Hi, saw that change but it seems that it doesn`t address this issue. It just threats SQL 2014 as 2008R2. It does fix some issues but not all of them. It seems that there are some differences between 2008 and 2014 on how eg. statistic indexes are stored in sys.index table but I`m not expert in this field and cant really tell what is the problem. Regards, Ivan
↧
↧

Created Unassigned: Only View Different Objects [15460]

April 23, 2015, 2:28 pm
$
0
0
Your tool is great. I really like the synchronization scripts, and how you can select just the objects you want to synchronize.

The only thing I really think it needs is a summary of the different db objects, where you can see just the objects the are new, updated, or to be deleted from the target database. I have also evaluated MssqlMerge and feel this is something it does very well. In that tool you can choose to see either all objects, or just the new objects, or the changed objects, or the deleted objects.

I have a large database and have to scroll through hundreds of tables to find the ones colored blue or green, it just makes it a bit difficult when the tool already knows which objects are different.

You probably already have this kind of feature scheduled for the next version, but if not, I give it a big +1.

Thanks for this free tool.
↧

Edited Unassigned: Feature Request: Only View Different Objects [15460]

April 23, 2015, 7:06 pm
$
0
0
Your tool is great. I really like the synchronization scripts, and how you can select just the objects you want to synchronize.

The only thing I really think it needs is a summary of the different db objects, where you can see just the objects the are new, updated, or to be deleted from the target database. I have also evaluated MssqlMerge and feel this is something it does very well. In that tool you can choose to see either all objects, or just the new objects, or the changed objects, or the deleted objects.

I have a large database and have to scroll through hundreds of tables to find the ones colored blue or green, it just makes it a bit difficult when the tool already knows which objects are different.

You probably already have this kind of feature scheduled for the next version, but if not, I give it a big +1.

Thanks for this free tool.
↧

Created Unassigned: 'Alter Destination' prompt shows source db [15461]

April 23, 2015, 7:11 pm
$
0
0
Per user brainboost's [pull request #8152]:(https://opendbiff.codeplex.com/SourceControl/network/forks/brainboost/FixMinorBug/contribution/8152)

question message box "ALTER Destination?" contained source db instead of the destination
↧
Viewing all 281 articles
Browse latest View live
Search