[dba-SQLServer] Connection string to Azure

[fhtapia at gmail.com]

 Hi David,

We run SQL Server in an Azure VM Vs. Running it as PaaS (platform as a
service) there are many additional tweaks one can manage on prem, but as
the link provided by Scott will show it’s a matter of configuring AD on
azure for access.

One other note, before any contracts are committed try a DR restore to a
locally hosted 2019 server to ensure backups work as advertised. In our
environment when we tested this feature in early 2019 we could not restore
to the community previews of 2019 yet, tho now that it’s generally
available it “should” work.

On PaaS backup and restore has worked for us during testing and remember
all your performance is now tied to these azure tiers, so if you need more
IO the client may end up spending more over the long run.

On Tue, Dec 3, 2019 at 5:12 AM <t.scott.marcus at gmail.com> wrote:

> David,
>
> << Is the only option to use a username and password for the connection
> string?
>
> No, you can use Active directory configured in Azure
>
>
> https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authent
> ication-configure?tabs=azure-powershell
> <https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure?tabs=azure-powershell>
>
> << Also, are there any potential issues/incompatibilities with running an
> SQL database in Azure?
>
> Potential issues/incompatibilities always exist when running something
> locally vs. that same thing being hosted offsite. Here are some off the top
> of my head...
>    1) Planning for loss of internet connection. While you should have done
> this for a locally hosted server, exactly how reliable is your internet
> connection vs. your internal infrastructure?
>    2) Version/configuration differences between what is on Azure and the
> environment you use to develop. You probably wont see any problem unless
> there are major differences but you should still keep this in mind.
>    3) It will be slower at transferring data to the client. This can be a
> big issue if your queries return lots of data.
>    4) While not exactly an Azure vs. locally hosted issue, what about your
> backup strategy? This is important since we developers cause lots of
> irreversible data loss by accident.
>
> Scott Marcus
>
> -----Original Message-----
> From: dba-SQLServer <dba-sqlserver-bounces at databaseadvisors.com> On Behalf
> Of David Emerson
> Sent: Tuesday, December 3, 2019 12:17 AM
> To: AccessDSQL <dba-SQLServer at databaseadvisors.com>
> Subject: [dba-SQLServer] Connection string to Azure
>
> Hi Listers,
>
>
>
> I have a database currently connected to SQL.  Here is the connection
> string:
>
>
>
> gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=DAVID-PC\DALYN2008;Initial Catalog=PRISM_UAT;Integrated
> Security=SSPI;"
>
>
>
> The client is exploring moving the SQL database to Azure.  However I am
> getting an error when I try to connect "Windows Logins are not supported in
> this version of SQL server."
>
>
>
> Is the only option to use a username and password for the connection
> string?
>
>
>
> Also, are there any potential issues/incompatibilities with running an SQL
> database in Azure?
>
>
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
>
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
> --
-Francisco <http://twitter.com/seecoolguy>