3
Vote

Failed to connect to Database

description

I've been using the SQL Azure Migration Wizard for a long time now, been working great. But today all of a sudden, it stopped working right.
I can connect fine to the server, but when I try to choose the Database, I get this exception (screenshot attached):
 

TITLE: Microsoft.SqlServer.Management.Sdk.Sfc

 
Failed to retrieve data for this request.
 
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

 

ADDITIONAL INFORMATION:
 
Operation not supported on version 11.0 SqlAzureDatabase. (Microsoft.SqlServer.SqlEnum)
 
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
 
Is this perhaps related to the fact that I changed the collation of the database? (it's not default Latin anymore). Though the last migration with that collation worked fine.
 
I tried both 2008 and 2012 versions (3.8.9 and 4.0.2). Same error.
 
Please help!

file attachments

comments

ghuey wrote Jun 12, 2012 at 1:44 PM

Hi Michael,

I have tried to reproduce this issuse and very sorry to say that I can't. I have both SQL Server 2008 and SQL Server 2012 on my machine and created a couple of databases using French collation. Everything works. So, just to make sure, you are talking about working with your Source Server not SQL Azure (or new name SQL Database) right? Is your database (.mdf & .ldf files) large / small and do not contain anything confidential? I was curious is maybe I could get hold of your database and see if I can reproduce the problem. Anyway, you can contact me offline at ghuey@microsoft.com and we can see what we can figure out.

Regards,
George

ghuey wrote Jul 6, 2012 at 7:47 PM

Hi,

I just wanted to follow up with you and say, yes you are correct. The issue is a collation / SMO issue and as far as I can tell at this time, the issue will have to be resolved by the Azure SQL Database group. While I can create a database with a specific collation, add tables and insert data, I can't script that database out. So, if possible, stick with default collation until the time that this issue gets resolved.

Regards,
George