1

We're currently developing against SQL Azure and have (unsuccessfully) tried to point a worker role to the master database in SQL Azure in order to automate database operations which require the master.

Unfortunately this doesn't seem to work.

A bit of background: "Allow other Windows Azure services to access this server" is enabled, and we have a firewall rule set up to enable this.

We suspect it may be a missing firewall rule that holds the key to this. Our worker role works against other SQL azure dbs, just not against the master at present...

If anyone can point me in the right direction I'd be grateful!

Cheers, Iago

Charlieface
  • 52,284
  • 6
  • 19
  • 43
iagomartinez
  • 172
  • 10
  • Can you post the specific error you're getting? Also if you RDP into the worker role VM can you telnet to the SQL Azure address and port? – HasaniH Sep 02 '11 at 14:11

1 Answers1

2

The issue with the master database turned out to be a red herring. The real issue was that I was using System.Data.SqlClient and Microsoft.SqlServer.Management objects to run a SQL batch script against the master (code in the style below).

var serverConnection = new ServerConnection(sqlConnection);
var server = new Server(serverConnection);
server.ConnectionContext.ExecuteNonQuery(sql);

After much banging our heads against a wall, the issue turned out to be that the required dlls to use these libraries just did not work in Azure (we kept getting errors about missing dependencies).

In the end, our solution to this was to break up the batch script into a number of subscripts (essentially splitting into parts wherever a GO statement was) and running using standard ADO.NET objects. This has turned out to be a better, more versatile solution so it has worked out OK for us after all!

iagomartinez
  • 172
  • 10