Azure to local SQL 2012 error

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

Azure to local SQL 2012 error

Postby lightyeare » Thu Sep 06, 2012 8:54 pm

I am getting an error comparing an Azure db to a local sql 2012 db that is empty. I've just done a successful compare and deployment with a different azure db and a different local sql 2012 db that was empty.

It throws error on Registering data sources - Reading indexes. The error is "property_list_id". Yes, that's it.

I am using Windows 8, SQL 2012 and the most recent version of SQL Compare 10.2.0.1337.
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Mon Sep 10, 2012 4:09 pm

Sorry for the inconvenience. Can you click on the "send error report" button and include your email address? This should give us some usable information about the error.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

ok

Postby lightyeare » Mon Sep 10, 2012 4:21 pm

did that about an hour before I posted here but I will do that again asap. the error details say: property_list_id. Hopefully more is being sent behind then scenes that isn't on the screen.

Working with this same azure database in SQL Data Compare also produces the same result.

Edit: support message successfully sent. I'd be happy to work with you in any way to try to resolve this error. Let me know.
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Wed Sep 12, 2012 12:18 pm

Can you try setting the SQL Compare project option "Ignore->Full-text indexing"? I think the text of the error message refers to a column name in the information schema that refers to a table containing fulltext indexes.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

sorry :(

Postby lightyeare » Wed Sep 12, 2012 12:32 pm

Tried Ignoring:
Full-text indexes
Indexes
The LOCK property of indexes
Constraint and index names
and then turned all the ignore options on.

Still fails same error.
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Wed Sep 12, 2012 3:35 pm

It looks like the SQL Compare code is treating the Azure database as if it were regular 2012, which has the index property "property_list_id" on full-text indexes. The source code indicates that it should gather this information on 2012 and ignore it on Azure... possibly SQL Compare is not detecting Azure correctly. Will have to look into that.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

Postby Brian Donahue » Wed Sep 12, 2012 3:39 pm

If you run this:
select SERVERPROPERTY('EngineEdition')
against the Azure database, SQL Compare expects it to be 5.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

Postby lightyeare » Wed Sep 12, 2012 3:41 pm

select SERVERPROPERTY('EngineEdition') returns 5
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby lightyeare » Wed Sep 12, 2012 3:46 pm

keep in mind the same error occurs for both SQL compare AND Sql Data compare
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Wed Sep 12, 2012 4:07 pm

Sure it would - they are both tied to the same schema reader code.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

Postby lightyeare » Wed Sep 12, 2012 4:16 pm

which would have been obvious if I had taken 2 seconds to think about it. let me know if I can provide any other info.
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Thu Sep 13, 2012 10:07 am

I'll let you know if I can think of anything...
I just did a SQL Compare between AdventureWorks on SQL 2102 vs Azure and did not get this error though.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

Postby lightyeare » Thu Sep 13, 2012 1:15 pm

yep, i am able to work just fine with one of our other azure dbs. also, i can work just fine with the azure db when i do the compare from our win2008 server. doesn't seem to work in my environment.
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Postby Brian Donahue » Fri Sep 14, 2012 5:36 pm

If it's any help, it looks like the live database in your error report is using SQL Server 2008 compatibility mode. I tried that in my test, but it did not reproduce the error. However, it may explain why you have this problem with some databases and not others. The bug that your error report got filed with mentions that it's a problem with SQL 2000 backward-compatibility.
Brian Donahue
 
Posts: 6668
Joined: Mon Aug 23, 2004 10:48 am

Postby lightyeare » Fri Sep 14, 2012 5:44 pm

i can work with the db fine using SQL Compare installed on our Window 2008 server.

so this is specifically related to my windows8 environment?
lightyeare
 
Posts: 8
Joined: Thu Sep 06, 2012 8:45 pm

Next

Return to SQL Compare 10

Who is online

Users browsing this forum: No registered users and 0 guests

cron