![]() New SQL Server releases may still have a variety of editions. The editions represented slightly different feature sets, but the core product was the same. There were various editions of each version of SQL Server, such as the Developer and Enterprise editions of SQL Server 2008. In the 1990s and into the 2000s, Microsoft SQL Server had only one product. The moniker code in the https address always matches the moniker name that is displayed in the versioning control. This parameter value is the versioning moniker code. There might or might not be any changes, and both cases are common.Įach article whose web address begins with has a parameter named ?view= appended to its address. When you click a different version, the displayed documentation suddenly changes to show the differences for the newly chosen version. Then click to choose any product and version combination you want. If you want to see the documentation for a different version of SQL Server, you click the expander arrow located at the end of the current version moniker. When you view any SQL documentation article by using our Docs website, the currently chosen versioning moniker is visible above the table of contents (TOC). The versioning monikers are assigned, or are explicitly embedded, at whatever degree of granularity makes sense for each given documentation file. This consolidation is made practical because we now assign versioning monikers to our SQL Server documentation files. Multiple versions in the same filesįor this reason and others, the documentation files for SQL Server 2016 are also for 2017, 2019, and probably for. This made fixing flaws and general maintenance more difficult. This old approach meant that if a flaw was discovered in the 2014 documentation, the flaw might also exist in 20. The 2014 copy was then edited during the product development cycle. For instance, the documentation for SQL Server 2014 began as a copy of the documentation for SQL Server 2012. History of separate file setsįor SQL Server 2014 and earlier versions, each version has its own full separate copy of the documentation files. We strive to avoid discrepancies between the Applies to line and the products aspect of our versioning system configurations. The Applies to line does not know about versions of products. For example, the product SQL Server could be indicated as relevant, while Azure SQL Database could be indicated as irrelevant to the article. ![]() ![]() On the same line, there follows a handy listing of SQL products with indicators of whether the article is relevant to the product. Most of the SQL Server articles have the words Applies to under their title. The system then displays the appropriate documentation. The system enables you to choose the product and version you are interested in. The versioning system knows about products and their versions. This article explains our versioning system for SQL documentation. ![]() Applies to: SQL Server Azure SQL Database Azure Synapse Analytics Analytics Platform System (PDW) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |