This topic lists the software requirements for Ventura SQL.

Ventura SQL Studio

Ventura SQL Studio runs on:

  • Windows 10
  • Windows 7
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012
  • Windows Server 2008


Ventura SQL Studio uses WPF for the UI.


Visual Studio project files

Ventura SQL Studio modifies Microsoft Visual Studio C# project files (.csproj) for adding the generated recordset classes to the C# project.


Ventura SQL studio's code generator was tested with project files that were written by Visual Studio 2017. Ventura can modify:

  • The "classic" project files;
  • The new ".Net Core" format project files.

Ventura SQL runtime DLLs

The runtime DLL (assembly) VenturaSQL.NETStandard.dll is compiled with Visual Studio 2017 as .NET Standard 2.0 class library.


.NET Standard 2.0 class libraries are compatible with multiple platforms. As such, .NET Standard is not a technology, but an API specification. .NET Standard 2.0 is supported on the following platforms:

  • .NET Framework 4.7.2. Older framework versions are known to have problems.
  • .NET Core 2.1
  • Mono 5.4
  • Xamarin.iOS 10.14
  • Xamarin.Mac 3.8
  • Xamarin.Android 7.5
  • UWP targetting Fall Creators Update (FCU, Build 16299) as the minimum version of your UWP project


The assembly VenturaSQL.AspNet.dll for ASP.NET is compiled with Visual Studio 2017 for .NET Framework version 4.7.2. DLLs compiled for this .NET Framework version are compatible with .Net Framework 4.7.2 or higher.


The assembly VenturaSQL.AspNetCore.dll for ASP.NET Core 2.1 is compiled with Visual Studio 2017.

ADO.NET Providers

Ventura is compatible with most, if not all, ADO.NET Providers.


Should you have a problem getting Ventura to work with a provider, then please contact us and we will try to find a solution.

Microsoft SQL Server

Ventura SQL is compatible with the following SQL Server versions:

  • Azure SQL Database
  • SQL Server 2017
  • SQL Server 2016
  • SQL Server 2014
  • SQL Server 2012
  • SQL Server 2008


Ventura probably works with SQL Server 2005 too, but compatibility is not tested by us.