Connecting to AzureSQL

[Stag76]

I'm currently using Lazarus 2.2.6, FPC 3.2.2 and ZEOSlib 7.2.14, using ntwdblib to connect to MSSQL DataBases
I now need to be able to connect to AzureSQL DataBases.
Which Versions of Lazarus and ZEOSlib are required for this connection, and what is the preferred connection method?

[paweld]

Zeos 8 and OleDB as the Protocol

[Stag76]

Thanks for that.
Will I also have to upgrade to the current Lazarus Software from Version 2.2.6, FPC 3.2.2

[paweld]

Will I also have to upgrade to the current Lazarus Software from Version 2.2.6, FPC 3.2.2

In general, I recommend using the most recent version of Lazarus/FPC, but it’s not required - Zeos 8 should work fine with FPC 3.2.2 and Lazarus 2.2.6

[Stag76]

Thanks again.

[Stag76]

Is there anything to be aware of when installing multiple versions of Lazarus in separate folders on the same machine.

[paweld]

Just make sure that each installation has its own configuration folder.

[Stag76]

Thanks for that.

Up until now, I've been using the 32-bit versions of Lazarus, converting Data from very
old Interbase and FireBird (Version 1.5) DataBases to SQL Server.
Is this a reason to continue with the 32-bit versions, or is a switch to the 64-bit Version
compatible with these DataBases, and therefore preferable.

[Thaddy]

SQL server itself is a 64bit database. I would not stick to 32 bit.

[Zvoni]

SQL server itself is a 64bit database. I would not stick to 32 bit.

The Database itself (as in: the actual Data-Files) is Bit-agnostic.

The Bitness matters for the Server-itself (the "program" offering the Database) and/or client libs accessing that Database

It doesn't matter if the Server itself runs on 64-Bit, but the clients on 32-Bit (or vice versa).

I know that from MySQL, where i actually did have the constellation of Server running 32-Bit, but the clients 64 Bit.
No issues whatsoever

[Thaddy]

There are no issues, but you should not encourage legacy platforms.
And Windows 32 bit IS a legacy platform for over 10 years.

[paweld]

I’ve only recently switched to FPC x86_64. Until now, I’d been using the 32-bit version, though I occasionally did cross-compilation to 64-bit for certain projects. Until the switch, I didn’t notice any shortcomings with the 32-bit version, but eventually, due to the large number of components, the Lazarus IDE stopped compiling for me, and I had to switch to x86_64.

If you use 32-bit libraries in your projects, I wouldn’t switch. If you use resources from rc files in your projects, I wouldn’t switch either - there’s a bug in stable version, that’s fixed in the fixes and trunk branches.

[Zvoni]

There are no issues, but you should not encourage legacy platforms.
And Windows 32 bit IS a legacy platform for over 10 years.

Agreed.
And i don't "encourage" use of legacy-platforms.
I was just correcting a misconception.

I could even say, that the Database-Server itself doesn't care, if the clients run on 32-Bit Linux, 64-Bit Windows, 128-Bit MacOS or 1024-bit LCARS,
as long as they  follow the communcation-protocol

[Stag76]

Thanks for all the Advice.

I've only changed my operating Version of Lazarus when I've changed hardware, so am
unsure of the best way to update an existing installation.

Which is the recommended method.
  1 . Uninstall Current Version, then install the New Version in the same folder (C:\Lazarus).
  2. Create a Secondary Installation in a Different Folder.

[Zvoni]

Second option