I am comparing two SQL Server databases and generating a sync script
for them. Version 2 has the tables grouped in different schemas, and
version 1 does not.
When the sync script gets generated to move V1 to V2 everything looks
good, except the schema name is not used. This causes many of the
statements to fail, and is basically a pain.
Is there any way to have the application append the schema name when
generating the sync script?
On Tue, Sep 15, 2009 at 1:18 PM, Scott McCormick <pike...@gmail.com> wrote:
> I am comparing two SQL Server databases and generating a sync script
> for them. Version 2 has the tables grouped in different schemas, and
> version 1 does not.
> When the sync script gets generated to move V1 to V2 everything looks
> good, except the schema name is not used. This causes many of the
> statements to fail, and is basically a pain.
> Is there any way to have the application append the schema name when
> generating the sync script?
> This is currently only supported for Oracle, but it shouldn't be too
> hard to add support for SQL Server.
> Marko
> On Tue, Sep 15, 2009 at 1:18 PM, Scott McCormick <pike...@gmail.com> wrote:
> > I am comparing two SQL Server databases and generating a sync script
> > for them. Version 2 has the tables grouped in different schemas, and
> > version 1 does not.
> > When the sync script gets generated to move V1 to V2 everything looks
> > good, except the schema name is not used. This causes many of the
> > statements to fail, and is basically a pain.
> > Is there any way to have the application append the schema name when
> > generating the sync script?
On Tue, Sep 15, 2009 at 5:10 PM, Scott McCormick <pike...@gmail.com> wrote:
> That would be great. Do you have a time frame for when that would
> occur?
> On Sep 15, 10:22 am, DB Solo <mhant...@gmail.com> wrote:
>> This is currently only supported for Oracle, but it shouldn't be too
>> hard to add support for SQL Server.
>> Marko
>> On Tue, Sep 15, 2009 at 1:18 PM, Scott McCormick <pike...@gmail.com> wrote:
>> > I am comparing two SQL Server databases and generating a sync script
>> > for them. Version 2 has the tables grouped in different schemas, and
>> > version 1 does not.
>> > When the sync script gets generated to move V1 to V2 everything looks
>> > good, except the schema name is not used. This causes many of the
>> > statements to fail, and is basically a pain.
>> > Is there any way to have the application append the schema name when
>> > generating the sync script?
This should be fixed for SQL Server now. There's a new option on the
sync script settings panel named 'Include schema name in statements'.
If you check this option, the sync script will contain the schema name
in all statements. Please download the new version from dbsolo.com/
preview and give it a try.
Marko
On Sep 15, 5:51 pm, DB Solo <mhant...@gmail.com> wrote:
> I can give a preview version probably later on this week.
> Marko
> On Tue, Sep 15, 2009 at 5:10 PM, Scott McCormick <pike...@gmail.com> wrote:
> > That would be great. Do you have a time frame for when that would
> > occur?
> > On Sep 15, 10:22 am, DB Solo <mhant...@gmail.com> wrote:
> >> This is currently only supported for Oracle, but it shouldn't be too
> >> hard to add support for SQL Server.
> >> Marko
> >> On Tue, Sep 15, 2009 at 1:18 PM, Scott McCormick <pike...@gmail.com> wrote:
> >> > I am comparing two SQL Server databases and generating a sync script
> >> > for them. Version 2 has the tables grouped in different schemas, and
> >> > version 1 does not.
> >> > When the sync script gets generated to move V1 to V2 everything looks
> >> > good, except the schema name is not used. This causes many of the
> >> > statements to fail, and is basically a pain.
> >> > Is there any way to have the application append the schema name when
> >> > generating the sync script?
|
