Justin Lettau

@lmeyer1 Thanks! I'm working on updating dependencies; I suspect that might fix this issue too.

@lmeyer1 Can you try with v3.0.0 and see if it's still an issue?

@DanielOverdevest Yeah, I do think it's a bug. I believe it has to do with how the queries are executed on push. I'm glad the `CREATE OR ALTER` works for...

@DanielOverdevest Can you reproduce this with in the latest version? The `push` command is designed to separate statements by the `GO` and execute each segment separately; So in theory this...

@DanielOverdevest Thanks!

@DanielOverdevest The only issue I am aware of with Azure SQL is regarding jobs (#65). Is the error your getting look related to jobs? If so, this config should address...

It looks like Windows Authentication is possible, so I've added that to the roadmap. In regards to connections in the `Web.config` ... a standard .NET XML config file is supported....

What do you mean? The connection to SQL is with user provided credentials, so we should have whatever permissions needed to execute.

It seems SQL Server 2016 introduced the `CREATE or ALTER` syntax, which avoids having to drop each object (and losing permissions). Will add this to idempotent options soon! https://blogs.msdn.microsoft.com/sqlserverstorageengine/2016/11/17/create-or-alter-another-great-language-enhancement-in-sql-server-2016-sp1/