I'm currently evaluating some features of Azure (beginning to wish I hadn't started).

After numerous connection issues via out internal firewalls/proxies etc I can connect to my Azure database. I quickly found out the LLBLGen designer doesn't play well with Azure due to a lack of metadata (found a post by David on the forums), I noticed the table designer in Management Studio doesn't start either and you get a scripting window (not sure if they are related).

I can create some entities to test and export the script and run the SQL scripts but only after removing "ON PRIMARY" from the creates due to Azure not allowing writing to the physical disk.

Is there a way to remove this at generation (easily) via the UI ? if not, 'maybe' it's worth adding a task option further down the line (if Azure gains more traction).

I'm just using the trial and we'll probably use Server2012 and the Azure pack anyway but Azure seems pretty pricey to me

Are you using LLBLGen v.4.1 trial, or v.3.5 as in your signature?

You are talking about SQL Azure (the PaaS database), not a SQL Server running on a VM (IaaS), correct?

Walaa wrote:

Are you using LLBLGen v.4.1 trial, or v.3.5 as in your signature?

You are talking about SQL Azure (the PaaS database), not a SQL Server running on a VM (IaaS), correct?

Hi,

My signature is a bit out of date.

It's 4.0 Final (26th Nov, 2013) and not SQL Server running on a VM.

NMackay wrote:

I'm currently evaluating some features of Azure (beginning to wish I hadn't started).

yeah, it is still a dark space outside the beaten paths, as with every typical ms technology

After numerous connection issues via out internal firewalls/proxies etc I can connect to my Azure database. I quickly found out the LLBLGen designer doesn't play well with Azure due to a lack of metadata (found a post by David on the forums), I noticed the table designer in Management Studio doesn't start either and you get a scripting window (not sure if they are related).

The main issue is indeed schema information which isn't available like in normal sql server. This is because sql azure isn't equal to normal sql server, as it's a distributed database. So to do database first work, you need a schema locally, and create the db for production online in azure from that schema.

I can create some entities to test and export the script and run the SQL scripts but only after removing "ON PRIMARY" from the creates due to Azure not allowing writing to the physical disk.

Is there a way to remove this at generation (easily) via the UI ? if not, 'maybe' it's worth adding a task option further down the line (if Azure gains more traction).

I'm just using the trial and we'll probably use Server2012 and the Azure pack anyway but Azure seems pretty pricey to me

At the moment the script indeed uses statements which are usable on the normal sql server, from sql server 2000 and up. We'll look at this in a future version.

yeah, it is still a dark space outside the beaten paths, as with every typical ms technology

LOL, Ain't that the truth

edit

ignore my last post about another issue, I'll start a new thread, sorry.