Buy SQL Server | Standard & Enterprise Pricing | Royal – Using SQL Server with an Internet Server
This product contains software derived from the Xerox Secure Hash Function. This product includes software from the zlib general purpose compression library. All rights reserved. These notices must be retained in any copies of any part of this documentation or software. Copyright Microsoft. Need more help? Expand your skills. Get new features first. Was this information helpful?
Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.
Didn’t match my screen. Incorrect instructions. In this case, you will have to download the files individually. You would have the opportunity to download individual files on the “Thank you for downloading” page after completing your download.
Files larger than 1 GB may take much longer to download and might not download correctly. You might not be able to pause the active downloads or resume downloads that have failed. Details Note: There are multiple files available for this download. Once you click on the “Download” button, you will be prompted to select the files you need. File Name:. Date Published:. File Size:. System Requirements Supported Operating System. Filename: x64 Package SqlCloudAdapter. You can download this database from this page, attach it to your SQL Server instance, and register it to use the new Semantic Search features.
NET Framework that provides application lifecycle services for database development and management. Filename: X86 and x64 Package tsqllanguageservice. This component also requires Windows PowerShell 2. NET Framework object model that enables software developers to create client-side applications to manage and administer SQL Server objects and services. The bcp utility bulk copies data between an instance of Microsoft SQL Server and a data file in a user-specified format. The bcp utility can be used to import large numbers of new rows into SQL Server tables or to export data out of tables into data files.
This component can be installed separately from the server to allow client applications to use these types outside of the server. Note: This component also requires Windows Installer 4. The component consists of a client-side DLL that is linked into a user application, as well as a set of stored procedures to be installed on SQL Server.
Run the self-extracting download package to create an installation folder. By doing this, cpu-intensive or long-duration tasks can be offloaded out of SQL Server to an application executable, possibly in another computer. The application executable can also run under a different Windows account from the Database Engine process. When pessimistic concurrency control is being used, SQL Server controls concurrent access by using locks.
Locks can be either shared or exclusive. Exclusive lock grants the user exclusive access to the data—no other user can access the data as long as the lock is held. Shared locks are used when some data is being read—multiple users can read from data locked with a shared lock, but not acquire an exclusive lock.
The latter would have to wait for all shared locks to be released. Locks can be applied on different levels of granularity—on entire tables, pages, or even on a per-row basis on tables.
For indexes, it can either be on the entire index or on index leaves. The level of granularity to be used is defined on a per-database basis by the database administrator. While a fine-grained locking system allows more users to use the table or index simultaneously, it requires more resources, so it does not automatically yield higher performance. SQL Server also includes two more lightweight mutual exclusion solutions—latches and spinlocks—which are less robust than locks but are less resource intensive.
SQL Server also monitors all worker threads that acquire locks to ensure that they do not end up in deadlocks —in case they do, SQL Server takes remedial measures, which in many cases are to kill one of the threads entangled in a deadlock and roll back the transaction it started.
The Lock Manager maintains an in-memory table that manages the database objects and locks, if any, on them along with other metadata about the lock. Access to any shared object is mediated by the lock manager, which either grants access to the resource or blocks it. SQL Server also provides the optimistic concurrency control mechanism, which is similar to the multiversion concurrency control used in other databases.
The mechanism allows a new version of a row to be created whenever the row is updated, as opposed to overwriting the row, i. Both the old as well as the new versions of the row are stored and maintained, though the old versions are moved out of the database into a system database identified as Tempdb.
When a row is in the process of being updated, any other requests are not blocked unlike locking but are executed on the older version of the row. If the other request is an update statement, it will result in two different versions of the rows—both of them will be stored by the database, identified by their respective transaction IDs.
The main mode of retrieving data from a SQL Server database is querying for it. The query declaratively specifies what is to be retrieved. It is processed by the query processor, which figures out the sequence of steps that will be necessary to retrieve the requested data. The sequence of actions necessary to execute a query is called a query plan.
There might be multiple ways to process the same query. For example, for a query that contains a join statement and a select statement, executing join on both the tables and then executing select on the results would give the same result as selecting from each table and then executing the join, but result in different execution plans. In such case, SQL Server chooses the plan that is expected to yield the results in the shortest possible time.
This is called query optimization and is performed by the query processor itself. SQL Server includes a cost-based query optimizer which tries to optimize on the cost, in terms of the resources it will take to execute the query.
Given a query, then the query optimizer looks at the database schema , the database statistics and the system load at that time. It then decides which sequence to access the tables referred in the query, which sequence to execute the operations and what access method to be used to access the tables. For example, if the table has an associated index, whether the index should be used or not: if the index is on a column which is not unique for most of the columns low “selectivity” , it might not be worthwhile to use the index to access the data.
Finally, it decides whether to execute the query concurrently or not. While a concurrent execution is more costly in terms of total processor time, because the execution is actually split to different processors might mean it will execute faster. Once a query plan is generated for a query, it is temporarily cached. For further invocations of the same query, the cached plan is used. Unused plans are discarded after some time. SQL Server also allows stored procedures to be defined.
Stored procedures are parameterized T-SQL queries, that are stored in the server itself and not issued by the client application as is the case with general queries.
Stored procedures can accept values sent by the client as input parameters, and send back results as output parameters. They can call defined functions, and other stored procedures, including the same stored procedure up to a set number of times. They can be selectively provided access to. Unlike other queries, stored procedures have an associated name, which is used at runtime to resolve into the actual queries.
Also because the code need not be sent from the client every time as it can be accessed by name , it reduces network traffic and somewhat improves performance. It exposes keywords for the operations that can be performed on SQL Server, including creating and altering database schemas, entering and editing data in the database as well as monitoring and managing the server itself. Client applications that consume data or manage the server will leverage SQL Server functionality by sending T-SQL queries and statements which are then processed by the server and results or errors returned to the client application.
For this it exposes read-only tables from which server statistics can be read. Management functionality is exposed via system-defined stored procedures which can be invoked from T-SQL queries to perform the management operation.
Linked servers allow a single query to process operations performed on multiple servers. It natively implements support for the SQL Server features including the Tabular Data Stream implementation, support for mirrored SQL Server databases, full support for all data types supported by SQL Server, asynchronous operations, query notifications, encryption support, as well as receiving multiple result sets in a single database session.
NET Framework. Unlike most other applications that use. NET Framework runtime , i. SQLOS provides deadlock detection and resolution services for. NET code as well. Managed code can also be used to define UDT’s user defined types , which can persist in the database. Managed code is compiled to CLI assemblies and after being verified for type safety , registered at the database.
After that, they can be invoked like any other procedure. Most APIs relating to user interface functionality are not available. However, doing that creates a new database session, different from the one in which the code is executing. NET provider that allows the connection to be redirected to the same session which already hosts the running code.
Such connections are called context connections and are set by setting context connection parameter to true in the connection string.
NET API, including classes to work with tabular data or a single row of data as well as classes to work with internal metadata about the data stored in the database. SQL Server also includes an assortment of add-on services. While these are not essential for the operation of the database system, they provide value added services on top of the core database management system. The SQL Server Machine Learning services operates within the SQL server instance, allowing people to do machine learning and data analytics without having to send data across the network or be limited by the memory of their own computers.
The services come with Microsoft’s R and Python distributions that contain commonly used packages for data science, along with some proprietary packages e. Analysts can either configure their client machine to connect to a remote SQL server and push the script executions to it, or they can run a R or Python scripts as an external script inside a T-SQL query.
The trained machine learning model can be stored inside a database and used for scoring. Used inside an instance, programming environment. The Service Broker, which runs as a part of the database engine, provides a reliable messaging and message queuing platform for SQL Server applications. Service broker services consists of the following parts: . The message type defines the data format used for the message.
This can be an XML object, plain text or binary data, as well as a null message body for notifications. The contract defines which messages are used in an conversation between services and who can put messages in the queue.
Download Microsoft® SQL Server® Feature Pack from Official Microsoft Download Center.MS SQL Server Licensing | CAL | Hosting by SolVPS®
No, customers must purchase Extended Security Updates separately. The cost of Extended Security Updates is not included in the price calculation of the Unified Support agreement. On-site or proactive support will only be available to a customer if it is part of their Unified Support agreement. Yes, organisations which have purchased Extended Security Updates can submit support incidents using any Microsoft Support offering, including Unified and Premier Support.
Microsoft Partners are also able to submit tickets on behalf of their customers as long as the customer has purchased Extended Security Updates, though partners will need a support agreement in place to do so.
All customers must call Microsoft Support in order to place a request for a technical support incident. As we continue to work to fully automate the validation process, the tech routers will validate whether a customer purchased Extended Security Updates. Once the customer is validated, a case will be created and routed to the appropriate queue for technical support.
Customers should provide their Enterprise Agreement number or full customer name for validation. If an investigation determines that resolution requires product enhancement available in a recent release, then a request will be made to the customer to upgrade to a more recent release where the capability is already available.
See online servicing for more details. Extended Security Updates are not supported in offline servicing mode. Applying Extended Security Updates in offline servicing mode will generate an error and updates will fail. The Wsusscn2. The latest Wsusscn2.
Windows Server: Customers can leverage existing on-premises licence investments to save on Azure Virtual Machines. Pricing is based on per core pricing, based on the number of virtual cores in the hosted virtual machine, and subject to a minimum of 16 licences per instance for Windows Server and four for SQL Server. Customers cannot apply them to non-covered databases or share them with hosters. The following describes pricing for Extended Security Updates in various hosted scenarios.
Azure Pricing: Cost included in standard virtual machine rate SA or subscription required? The Extended Security Updates offer does not include technical support. Customers can use existing support agreements for questions. However, free updates in Azure is the more attractive offer. They are Security Updates only. Customers can install Extended Security Updates using the tools and processes they are using today.
The only difference is that the system must be unlocked for the updates to install. On-premises customers that purchase Extended Security Updates will receive an add-on key to activate Extended Security Updates through the volume licensing portal VLSC or alternatively, go to Azure Portal to do download keys link to service. Specific KB information can be found in that blog post.
This is also the process that customers will need to follow for Azure Stack. They do not replace the current product activation key e. Customers will need to install a new Extended Security Updates key each year they have Extended Security Updates deployed. There is also time required for your organisation to plan and deploy those MAK keys prior to deploying the security updates. Be sure to take this time frame in mind as you consider purchasing ESU licences.
Pre-patched Windows Server R2 images will also be available from the Azure gallery. If an Azure Virtual Machine is not configured to receive automatic updates, then the on-premises download option applies. For more information about automatic updates, see Manage Windows updates by using Azure Automation. Microsoft recommends applying Extended Security Update patches as soon as they are available to keep your environment protected.
For specific questions about update channels, and the instance registration and download process, please contact your Microsoft Technical Account Manager or Support resource. Windows Server SP2: The support will be in an upcoming release, but the same steps will apply. All rights reserved. Installation ID: Confirmation ID for product 77dbbcd7-a3ab-a9c6de0 deposited successfully.
Customers may use their preferred tools for software and hardware inventory. Find links to inventory tools from Microsoft and our partners on the Azure migration centre site. Customers can migrate workloads from a VMware-based virtual machine on-premises to Azure Virtual Machines using Azure Site Recovery or many partner tools.
Another option is the new VMware on Azure solution, for a dedicated hosting experience. Customers can also migrate to pay-as-you-go Azure Virtual Machines. Managed Instance also provides a version-less experience that takes away the need for manual security patching and upgrades.
It combines the rich SQL Server surface area with the operational and financial benefits of an intelligent, fully managed service. Customers can choose to modernise in-place with the same PaaS benefits when their workloads cannot move to Azure. Customers that are ready to upgrade, either in Azure or on-premises, can review the Azure Marketplace catalogue, as well as consult with their software vendor, to find the matrix of supported apps on all the Windows Server and SQL Server versions.
Customers should assess their application infrastructure before migrating any server applications. They can learn more about the recommended process in the Azure Migration Centre where you will learn how to leverage services like Azure Migrate to complete a readiness assessment including a cost estimate to run the application infrastructure in Azure. For further questions, work with your Microsoft partner, Microsoft Services or your Account team to evaluate application readiness.
Next year the only really supported version will be SQL extended support is only for Security fixes. I have one question. We have SSAS tabular — version. We have upgraded from to version. I guess this means I should also be testing against SQL when released before its features are introduced to Azure SQL and hope theres nothing breaking in there?!
How do others plan for something unknown? This is really beyond the scope of this blog post, unfortunately. Your email address will not be published. Post Comment. I love teaching, travel, cars, and laughing. Want to advertise here and reach my savvy readers? Last Updated 2 months ago Brent Ozar. Moving on. You use log shipping as a reporting tool, and you have tricky permissions requirements because they added new server-level roles that make this easier.
You still have to put in time to find the queries that are gonna get slower, and figure out how to mitigate those. This meant you could write one version of your application that worked at both your small clients on Standard, and your big clients on Enterprise.
This grid has a great comparison of what changed with columnstore over the years. Remember, there are no more Service Packs, just Cumulative Updates.
You have a zero-RPO goal and financial risks — because added a new minimum commit replica setting on AGs that will let you guarantee commits were received by multiple replicas You want easier future upgrades — because starting with , you can have a Distributed Availability Group with different versions of SQL Server in it. You need high performance columnstore queries — because we got a lot of cool stuff for batch mode execution plans.
Some of the clustering bugs have really made my eyebrows raise. That makes me pretty uncomfortable for mission-critical production environments. You heavily rely on user-defined functions — because can dramatically speed those up , although you need to do a lot of testing there, and be aware that Microsoft has walked back a lot of the improvements. You rely heavily on table variables, and you can change the code — those are getting better too. Your DR plan is Azure Managed Instances — because will theoretically make it possible to fail over to MIs, and more importantly, fail back when the disaster is over.
Is it supposed to smell this bad? Leave new Venkata Jayaram Peri. Henrik Staun Poulsen. Brent Ozar. If not, what options do I have to make it go faster? Jeff Moden. And enjoy the journey! Thanks for understanding. Kasper Brandenburg. Mike Care. Joseph Gooch. Dave U. Koen Verbeeck. Stefan Gabriel. Alex Friedman. Matt H. Adam Seniuk. You are awesome Brent! Thanks again. Ron S. Craig S. Ted Gman. Muhammad Aatif Fasihi. John Bigler. Carl E Thompson. Give er a read.
Jessica M. Luis Agustin Azario. Kannan Chandrasekaran. Timothy King. I was going to consider and just go for it. Your thoughts? I sent you a contact form. Definitely interested in consulting.
Brandon Forest. Rudy Panigas. So no idea when the next major release will be either I suppose. Build, test and demonstrate applications in a non-production environment with this full-featured edition of SQL Server View the comprehensive feature comparison of SQL Server editions for feature details and limitations.
Basic high availability: two-node single database failover, non-readable secondary. Advanced high availability: Always On Availability Groups, multi-database failover, readable secondaries. Data marts and data warehousing: partitioning, data compression, change data capture, database snapshot. Basic corporate business intelligence: basic multi-dimensional models, basic tabular model, in-memory storage mode . Advanced corporate business intelligence: advanced multi-dimensional models, advanced tabular model, DirectQuery storage mode, advanced data mining .
Basic Machine Learning integration: connectivity to open source Python and R, limited parallelism . Use a secured, cost-effective, highly scalable data platform for public websites — available to third-party hosting service providers only.
SQL Server licensing makes choosing the right edition simple and economical. Pay by processing power for mission-critical applications as well as business intelligence. Add self-service BI on a per user basis. Cloud-optimised licensing with the ability to license virtual machines, and the flexibility to move from server to server, to hosters, or to the cloud, on the operating system of your choice.
Get outstanding value at any scale compared to all major vendors. The Enterprise edition offers all product features and capabilities with no costly add-ons required to run your most demanding applications. For sales questions, contact a Microsoft representative on in the United States or in Canada. Comprehensive, mission-critical performance for demanding database and business intelligence requirements.
Provides the highest service and performance levels for Tier-1 workloads. Core data management and business intelligence capabilities for non-critical workloads with minimal IT resources. Full-featured version of SQL Server software that allows developers to cost-effectively build, test and demonstrate applications based on SQL Server software.
Free download. Secure, cost effective and highly scalable data platform for public websites. Available to third-party software service providers only. Parallel data warehouse is part of the Microsoft Analytics Platform System. For your specific pricing, contact your Microsoft reseller. See the product use rights for details.
SQL Server Standard edition is available to buy online. Easily upgrade to Enterprise edition for comprehensive high-end datacentre capabilities. Get started with SQL Server Plan a SQL Server installation. Install SQL Server Gain expertise with SQL Server training and certification. Explore SQL Server virtual labs. Quickly get started with code samples on GitHub. Visit the SQL Server migration forums. Learn more about SQL Server end of support. Download the Microsoft Assessment and Planning Toolkit.
Read the SQL Server upgrade technical guide. Download the Data Migration Assistant. Contact Microsoft support. SQL Server documentation library. Ask a question in the SQL Server forums. SQL Server on Twitter. SQL Server on Facebook. Try now Watch now. Your choice of language and platforms Build modern applications using the language of your choice, on-premises and in the cloud, now on Windows, Linux and Docker containers.
Industry-leading performance Take advantage of breakthrough scalability, performance and availability for mission-critical, intelligent applications and data warehouses. Least vulnerable database Protect data at rest and in motion with the least vulnerable database over the last seven years in the NIST vulnerabilities database.
Get the essential guide to data in the cloud. Featured SQL Server resources. Get the kit. SQL Server technical eBooks Get the technical resources, documentation and code samples you need to support all areas of your data estate — from discovery and research to implementation and maintenance. Get the eBooks.
Its name is entirely descriptive, it being server software that responds to queries in the SQL language. As of July [update] , the following versions are supported by Microsoft:. From SQL Server onward, the product is supported on x64 processors only and must have 1.
The RTM version is Microsoft makes SQL Server available in multiple editions, with different feature sets and targeting different users. These editions are:  . The protocol layer implements the external interface to SQL Server. TDS is an application layer protocol, used to transfer data between a database server and a client.
Initially designed and developed by Sybase Inc. Consequently, access to SQL Server is available over these protocols. Data storage is a database , which is a collection of tables with typed columns. SQL Server supports different data types, including primitive types such as Integer , Float , Decimal , Char including character strings , Varchar variable length character strings , binary for unstructured blobs of data , Text for textual data among others.
In addition to tables, a database can also contain other objects including views , stored procedures , indexes and constraints , along with a transaction log.
A SQL Server database can contain a maximum of 2 31 objects, and can span multiple OS-level files with a maximum file size of 2 60 bytes 1 exabyte. Secondary data files, identified with a.
Log files are identified with the. Storage space allocated to a database is divided into sequentially numbered pages , each 8 KB in size. A page is marked with a byte header which stores metadata about the page including the page number, page type, free space on the page and the ID of the object that owns it. The page type defines the data contained in the page. This data includes: data stored in the database, an index, an allocation map, which holds information about how pages are allocated to tables and indexes; and a change map which holds information about the changes made to other pages since last backup or logging, or contain large data types such as image or text.
A database object can either span all 8 pages in an extent “uniform extent” or share an extent with up to 7 more objects “mixed extent”. A row in a database table cannot span more than one page, so is limited to 8 KB in size. However, if the data exceeds 8 KB and the row contains varchar or varbinary data, the data in those columns are moved to a new page or possibly a sequence of pages, called an allocation unit and replaced with a pointer to the data.
For physical storage of a table, its rows are divided into a series of partitions numbered 1 to n. The partition size is user defined; by default all rows are in a single partition.
A table is split into multiple partitions in order to spread a database over a computer cluster. Rows in each partition are stored in either B-tree or heap structure.
If the table has an associated, clustered index to allow fast retrieval of rows, the rows are stored in-order according to their index values, with a B-tree providing the index. The data is in the leaf node of the leaves, and other nodes storing the index values for the leaf data reachable from the respective nodes.
If the index is non-clustered, the rows are not sorted according to the index keys. An indexed view has the same storage structure as an indexed table. A table without a clustered index is stored in an unordered heap structure. However, the table may have non-clustered indices to allow fast retrieval of rows. In some situations the heap structure has performance advantages over the clustered structure. Both heaps and B-trees can span multiple allocation units.
Any 8 KB page can be buffered in-memory, and the set of all pages currently buffered is called the buffer cache. The amount of memory available to SQL Server decides how many pages will be cached in memory.
The buffer cache is managed by the Buffer Manager. Either reading from or writing to any page copies it to the buffer cache. Subsequent reads or writes are redirected to the in-memory copy, rather than the on-disc version. The page is updated on the disc by the Buffer Manager only if the in-memory cache has not been referenced for some time. Each page is written along with its checksum when it is written. When reading the page back, its checksum is computed again and matched with the stored version to ensure the page has not been damaged or tampered with in the meantime.
SQL Server allows multiple clients to use the same database concurrently. As such, it needs to control concurrent access to shared data, to ensure data integrity—when multiple clients update the same data, or clients attempt to read data that is in the process of being changed by another client. SQL Server provides two modes of concurrency control: pessimistic concurrency and optimistic concurrency.
When pessimistic concurrency control is being used, SQL Server controls concurrent access by using locks. Locks can be either shared or exclusive. Exclusive lock grants the user exclusive access to the data—no other user can access the data as long as the lock is held. Shared locks are used when some data is being read—multiple users can read from data locked with a shared lock, but not acquire an exclusive lock.
The latter would have to wait for all shared locks to be released. Locks can be applied on different levels of granularity—on entire tables, pages, or even on a per-row basis on tables. For indexes, it can either be on the entire index or on index leaves. The level of granularity to be used is defined on a per-database basis by the database administrator. While a fine-grained locking system allows more users to use the table or index simultaneously, it requires more resources, so it does not automatically yield higher performance.
– Microsoft sql server 2014 standard 2 core license free
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Installation of SQL Server is supported on x64 processors only.
It is no longer supported on x86 processors. The table in this section lists the minimum software requirements for running SQL Server. There are also recommended configuration options for optimal performance. There are additional hardware and software requirements for the PolyBase feature. For more information, see Get started with PolyBase. The following table shows which editions of SQL Server are compatible with which versions of Windows:.
WOW64 Windows bit on Windows bit is a feature of bit editions of Windows that enables bit applications to run natively in bit mode. Applications function in bit mode, even though the underlying operating system is a bit operating system. Windows client operating systems, for example Windows 10 and Windows 8.
All SQL Server features are supported on bit client operating systems. On supported bit client operating systems Microsoft supports the following features:. Windows Server R2 and later server operating systems are not available as bit architectures. All supported server operating systems are only available as bit. All features are supported on bit server operating systems. This requirement applies even if you install SQL Server components to a non-default drive. Actual hard disk space requirements depend on your system configuration and the features that you decide to install.
The following table provides disk space requirements for SQL Server components. For security reasons, we recommend that you do not install SQL Server on a domain controller. SQL Server Setup will not block installation on a computer that is a domain controller, but the following limitations apply:.
After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller. After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member. SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
SQL Server is not supported on a read-only domain controller. In this scenario, Setup will fail. A SQL Server failover cluster instance is not supported in an environment where only a read-only domain controller is accessible.
Alternatively, you can create an Azure virtual machine already running SQL Server though SQL Server on a virtual machine will be slower than running natively because of the overhead of virtualization.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode. Table of contents. Important There are additional hardware and software requirements for the PolyBase feature.
Note This restriction also applies to installations on domain member nodes. Submit and view feedback for This product This page. View all page feedback. In this article. Disk space requirements will vary with the SQL Server components you install.
For more information, see Hard Disk Space Requirements later in this article. For information on supported storage types for data files, see Storage Types for Data Files. Read-only, mapped, or compressed drives are blocked during installation.
Minimum: x64 Processor: 1. SQL Server NET Framework 4. SQL Server setup automatically installs. NET Framework. You can also manually install. NET Framework from Microsoft. For more information, recommendations, and guidance about.
Windows 8. Note: Support for. You can upgrade to. NET 4. All frameworks with major version 4 do an in-place upgrade, and they are backward compatible. For more information, check Download. Net Framework 3.
Supported operating systems for SQL Server have built-in network software. Note: VIA protocol is not supported on failover clusters. Clients or applications running on the same node of the failover cluster as the SQL Server instance, can use Shared Memory protocol to connect to SQL Server using its local pipe address.
However this type of connection is not cluster-aware and will fail after an instance failover. It is therefore not recommended and should only be used in very specific scenarios. Important: The VIA protocol is deprecated. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.