Windows 10: Transferring SQL Client Access Licenses from primary server to secondary server.

sejalmaurya · Apr 10, 2019

If we go with SQL Server + CAL base licensing . can we transfer SQL CALs from my primary server to secondary when my primary server fails or down ?

If we go for SQL Server + CAL base licensing what all SQL CAL licenses need to be installed(need to buy) on primary and Secondary server. ?

If we go for SQL Server Core Base licensing what all SQL licenses need to be installed(need to buy) on primary and Secondary server ?

can we use SQL core base license as a primary and SQL CAL base license as secondary or vice versa ?

***Modified title from: SQL primary and secondary server***

:)

Cluster Head · Apr 10, 2019

Easily bring your SQL Server licenses to Azure VMs

Easily bring your SQL Server licenses to Azure VMs

I am super exited to announce that starting today, Microsoft Enterprise Agreement customers can bring existing licenses to run SQL Server on Azure Virtual Machines. Since the launch of Azure Virtual Machines, customers can already run SQL Server on Azure Virtual Machines through several existing SQL Server images available in the Azure Gallery, or bring their own images to Azure. These images and capabilities will continue to be supported so customers can continue to take advantage of pay per use licensing for SQL Server on Azure Virtual Machines.

Starting this week, customers with Enterprise Agreement who already have SQL Server Licenses, can use them on Azure Virtual Machines with Microsoft-certified (BYOL) gallery images. These images will not charge for SQL Server licensing, just for compute cost.

With this announcement, Microsoft Enterprise Agreement customers will have access to new set of gallery images that they can use with their existing SQL Server licenses and deploy VMs with them. This provides the flexibility, convenience, ease of use and additional cost savings to Microsoft Enterprise Agreement customers. Reusing an existing SQL Server license reduces the cost for our customers running SQL Server workloads continuously or for extended periods of time.

There is no need to build custom images to migrate SQL Server to Azure Virtual Machines. Instead, customers can provision VMs from one of the above images and add their existing license – Enterprise Agreement subscription is required. Customers can also leverage these Microsoft-certified BYOL images to leverage the rich automation features of Portal, Azure QuickStart GitHub templates (i.e. storage configuration, optimization for Transactional Processing, Data Warehousing, Automated Backup and automated Patching). Customers can also choose to deploy their SQL Server VMs through the gallery directly or using their favorite client tool such as Azure PowerShell, Azure CLI – Command Line Interface or through the Azure SDKs.

In response to customer feedback, you can now login to your Enterprise Agreement subscription and provision SQL Sever based VMs using your existing license(s). Learn more on our documentation page.
Click to expand...

Source: https://azure.microsoft.com/en-us/bl...0531_479823347

Brink · Apr 10, 2019

SQL Server + C#: What’s new

With the release of SQL Server v.Next public preview on Linux and Windows, the ability to connect to SQL Server on Linux, Windows, Docker or macOS (via Docker) makes cross-platform support for all connectors, including .NET Framework and .NET Core SqlClient, even more important. To enable C# developers to use the newest SQL Server features, we have been updating SqlClient with client-side support for new features.

In .NET Framework, we have provided client-side support for Always Encrypted and added Azure Active Directory as an authentication method. We’ve also added a new connection string parameter called “Pool Blocking Period.” It can be used to select the behavior of the blocking period when connecting to Azure SQL Database and SQL Server. Many applications that connect to Azure SQL Database need to render quickly, and the exponential blocking period can be problematic, especially when throwing errors. By adding the Pool Blocking Period parameter, we aim to improve the experience for connections to Azure SQL Database. Learn more about the new parameter here.

.NET Core is the cross-platform, open-source implementation of the .NET Framework. The project includes CoreFX, the foundational libraries of .NET Core. Cross-platform support allows developers to seamlessly run applications on their operating system of choice, regardless of the platform it was developed on. For example, an app developed on Windows can be deployed to macOS and Linux, without ever having to port any code. To connect apps written in .NET Core to SQL Server (hosted anywhere), developers can use System.Data.SqlClient available in CoreFX. By developing in .NET Core on GitHub, we have been able to get feedback quickly and are actively working to enable the breadth of application scenarios and workloads.

Get started today

Check out CoreFX on GitHub! Make pull requests and let us know what you think.

Try the new getting started tutorials that show you how to:

Install SQL Server on Linux/macOS/Docker/Windows

Create a simple app using C# and other popular programming languages with SQL Server

Create a simple app using popular web frameworks and Object Relational Mapping (ORM) frameworks with SQL Server

Try out some cool SQL Server features that can make your apps shine

Connect with us

Join the conversation at https://gitter.im/mssqldev.

Sign up to stay informed about new SQL Server on Linux developments.

Learn more

Visit the Connect(); webpage to watch overview, security, high-availability and developer tools videos about SQL Server on Linux on demand.

Visit the webpage for the next release of SQL Server.

Other videos in this series

SQL Server + Node.js: what’s new

SQL Server + Java: what’s new

SQL Server + PHP: what’s new

SQL Server + Python: what’s new

Watch the to see how to get started with SQL Server on Linux in less than a minute.

SQL Server on Linux: use SQL Tools with SQL Server

Click to expand...

Source: SQL Server + C#: Whats new | SQL Server Blog

lgentry · Apr 10, 2019

Help me understand SQL Server

While trying to understand intermittent freezes in my Windows 10 that require hard reboots to recover from I was looking at my event viewer trying to find the culprit. Although I have not yet narrowed down the problem (there are several different errors) I came across several events related to SQL Server "insufficient system memory in resource pool 'internal' to run this query". I'm running a quad core i5 machine with 8 gb of ram. Looking at my list of installed programs I notice that I have the following:

SQL Server 2005 Compact Edition
SQL Server 2008 Setup Support Files
SQL Server 2012 Native Client
SQL Server 2014 Setup
SQL Server 2014
SQL Transact SQL Scriptdom
SQL Server Browser for SQL Server 2014

I've tried to read about exactly what SQL Server is and it's as clear as mud to me. Can someone help me understand what it is? Do I need to have all those versions installed? Thanks in advance for your assistance.

Windows 10: Transferring SQL Client Access Licenses from primary server to secondary server.

Transferring SQL Client Access Licenses from primary server to secondary server.

Transferring SQL Client Access Licenses from primary server to secondary server.

Transferring SQL Client Access Licenses from primary server to secondary server.

Transferring SQL Client Access Licenses from primary server to secondary server. - Similar Threads - Transferring SQL Client

Transferring of Windows Server 2012, SQL Server 2012 and Sharepoint Servers 2013 license...

Transferring of Windows Server 2012, SQL Server 2012 and Sharepoint Servers 2013 license...

Transferring of Windows Server 2012, SQL Server 2012 and Sharepoint Servers 2013 license...

License for Windows Server and SQL Server

License for Windows Server and SQL Server

SQL Server 2014 License?

SQL Server 2014 License?

Downloading SQL and accessing server

SQL primary and secondary server