Microsoft will address only problems that are reproducible on a supported configuration. For more information, see the documentation page for container deployment. For more information about how the operating system vendors support the components in the container and the host operating system, see the following channels:. Red Hat Container Support Policy. SQL Server deployments in Windows containers are not covered by support.
For development and testing, create your own custom container images to work with SQL Server in Windows containers. Sample files are available on GitHub but are provided for reference only. If the issue does not occur after the removal of customization, then Microsoft will not support the customization or custom script. These changes or similar changes are supported to help create your own custom SQL container image. You try building a customized image on top of any Linux platform that is not mentioned in the supported platforms documentation.
This applies to the volumes that store the database files and program binaries. When you set up a high availability solution for SQL Server on Linux, review the support policies of the OS vendor that are specific to high availability. A Linux cluster uses fencing to return the cluster to a known state. The correct manner in which to configure fencing depends on the distribution and the environment.
Currently, fencing is not available in some cloud environments. For more information, see the following OS vendor policies and recommendations:. If you try to use components or features that are listed in the notes as unsupported, you might experience unexpected symptoms and errors.
When you use a combination of features for your application or solution, make sure that the interoperability between the features is documented as supported. Microsoft provides technical support and product fixes for SQL Server components that are deployed on supported operating system, file systems, hypervisors, and hardware architectures in accordance with the product documentation.
Microsoft may provide limited or no technical support for SQL Server software components that are deployed on unsupported operating systems, file systems, hypervisors, and hardware platforms. Microsoft Professional Support incidents cover the entire product lifecycle both mainstream and extended support. For more info, search for your product to review lifecycle eligibility. Visit account. The support professional will agree on the definition of the problem with you when you raise the support incident.
The incident will be closed after the support professional has delivered one or more suggested solutions to you. If the support professional is unable to deliver a solution, you'll be notified and the case will be closed as unresolved.
The billing status of an unresolved case will be at the discretion of Microsoft. Customers may request to close a case before it's resolved; however, the billing status of the incident is at the discretion of Microsoft. When you submit a new incident, you'll need to log on with the same Microsoft account used to purchase the 5-pack of incidents.
Submit incidents online. If you don't have access to the Microsoft account used to purchase the 5-pack, contact us. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Microsoft Lifecycle Policy Consistent and predictable guidelines for the availability of support throughout the life of a product. The availability of support for mounted folders depends on the version of SQL Server and on whether the instance of SQL Server is a stand-alone or clustered instance:.
Note Mounted folders are also known as any of the following:. However, the SQL Server Setup program requires the base drive of a mounted drive to have an associated drive letter. If the base drive of a mounted drive does not have an associated drive letter, the Setup program will assign the next available drive letter to the drive. Note If all the drive letters are already assigned, the Setup program will fail. For more information, click the following article number to view the article in the Microsoft Knowledge Base:.
The clustered installations of SQL Server are limited to the number of available drive letters. Therefore, if you use only one drive letter for the operating system, and if all other drive letters are available as normal cluster drives or as cluster drives that are hosting mount points, you are limited to no more than 25 instances of SQL Server per failover cluster.
A mounted volume, or mount point, lets you to use a single drive letter to refer to many disks or volumes. For example, if you have a drive letter R: that refers to a regular disk or volume, you can connect or "mount" additional disks or volumes as directories under drive letter R: without the additional disks or volumes requiring drive letters of their own. Additional mount point considerations for SQL Server failover clustering include the following:.
SQL Server Setup requires that the base drive of a mounted drive has an associated drive letter. For failover cluster installations, this base drive must be a clustered drive. Volume GUIDs are not supported in this release. The base drive is the drive that is assigned the drive letter. The base cannot be shared among failover cluster instances.
0コメント