Haven't done this with Azure but in a "normal" environment I've created the SP in the database using a similar naming convention as what Kentico uses but with my custom names. Then I create a custom document type and add a custom query within the new document type that calls this stored procedure. This way I can use a custom query webpart to display the data without having to write any code. This way will also allow me to write as many transformations as I'd like as well even if you getting a different dataset each time.

Hi it all depends on what you are trying to do. We generally store our data in custom tables and then use the API to retrieve/set the data.

If you are creating very stand alone tables yourself you can still create custom tables based on an existing database table and use the API to get the data in and out.

If you are set on using stored procedures and your own processes and or tables then just use a sensible naming convention.

Azure SQL does handle general stored procedures but not every type of stored procedures in MSSQL. Here is a link to show what's supported and what isn't...

http://msdn.microsoft.com/en-us/library/windowsazure/ee336237.aspx

Any questions just ask,

Thanks,

Matt