Crossing Azure Borders

  • Andrew..Peterson (11/6/2015)


    xsevensinzx (11/6/2015)


    I wish I could try it more, but AWS has such a strong offering and flexibility for my distributed processing needs.

    That and the fact I can spin up a entire cluster for distributed processing a single script controlled by a SSIS package. I don't know if Microsoft offers similar, but would be nice to know if that's possible through API's too.

    I have not had a chance to work with it, but the Azure SQL Data Warehouse is suppose to be based on/using AWS.

    Yeah, they are trying to compete. The thing with AWS is they have multiple services that have a great deal of flexibility. At least that what it feels like on the top layer. Maybe Azure has similar, but I didn't really see it.

    For example, the link above may compare to AWS EMR, which is like Hadoop on demand. You can spin up and tare down a 30-node Hadoop cluster on the fly with a single script with SQL Server. You have full control over the instance that is running your services with a wide variety of high/low memory and high/low compute instances running Linux.

    It's very slick and affordable compared to Redshift, which is a beast.

  • Azure: still can't legally use it for a majority of my clients. Still has a ton of issues that you don't find with self hosted servers, missing features, bad documentation, yada, yada, yada.

    Here's some mixed reviews:

    https://www.reddit.com/r/SQLServer/comments/3rbo93/why_is_azure_sql_server_so_brokencrippled/

  • chrisn-585491 (11/9/2015)


    Azure: still can't legally use it for a majority of my clients. Still has a ton of issues that you don't find with self hosted servers, missing features, bad documentation, yada, yada, yada.

    Here's some mixed reviews:

    https://www.reddit.com/r/SQLServer/comments/3rbo93/why_is_azure_sql_server_so_brokencrippled/

    I'm not sure there are a ton of issues. There are some, and a few of them will never be fixed, like Filestream, and not likely Service Broker. Documentation is a bit of a mess, and gets worse as things rev, but that initial post isn't remotely close to some evaluation of Azure SQL DB.

    It's certainly not for some applications. Not sure if it's most.

  • SQL Azure Linked Servers - note about security:

    In order to successfully create a SQL Azure Linked Server you should perform the following in SQL Azure database:

    -- run this script from <Azure SQL Database>|Databases|System Databases|master node via New Query

    CREATE LOGIN [test] WITH password='********'

    GO

    CREATE USER [test] FOR LOGIN [test] WITH DEFAULT_SCHEMA=[dbo]

    GO

    -- run this script from <Azure SQL Database>|Databases|<DB Name> node via New Query

    CREATE USER [test] FOR LOGIN [test] WITH DEFAULT_SCHEMA=[dbo]

    GO

    EXEC sp_addrolemember 'db_owner', 'test';

    GO

    EXEC sp_addrolemember 'db_securityadmin', 'test';

    GO

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply