SQL Server 2. 01. Service Pack 1 (SP1) released !!! With cloud first strategy, the SQL Product Team has observed great success and adoption of SQL Server 2. Today, we are even more excited and pleased to announce the availability of SQL Server 2. Service Pack 1 (SP1). With SQL Server 2. SP1, we are making key improvements allowing a consistent programmability surface area for developers and organizations across SQL Server editions. This will enable you to build advanced applications that scale across editions and cloud as you grow. Developers and application partners can now build to a single programming surface when creating or upgrading intelligent applications, and use the edition which scales to the application’s needs. In addition to a consistent programmability experience across all editions, SQL Server 2. SP1 also introduces all the supportability and diagnostics improvements first introduced in SQL 2. SP2, as well as new improvements and fixes centered around performance, supportability, programmability and diagnostics based on the learnings and feedback from customers and SQL community. SQL Server 2. 01. SP1 also includes all the fixes up to SQL Server 2. RTM CU3 including Security Update MS1. Following is the detailed list of improvements introduced in SQL Server 2. SP1. The following table compares the list of features which were only available in Enterprise edition which are now enabled in Standard, Web, Express, and Local. DB editions with SQL Server 2. ![]() SP1. This consistent programmatically surface area allows developers and ISVs to develop and build applications leveraging the following features which can be deployed against any edition of SQL Server installed in the customer environment. The scale and high availability limits do not change, and remain as–is for lower editions as documented in this MSDN article.* Requires SQL Server agent which is not part of SQL Server Express Editions** Requires creating filestream file groups which is not possible in Local DB due to insufficient permissions. Boosting transaction processing using Storage Class Memory in Windows Server 2. One of the most significant performance overheads for high transactional workloads systems is committing to the transaction log. This is especially true when employing In- Memory OLTP tables which remove most other bottlenecks from high update rate applications. SQL Server 2. 01. SP1 adds a significant new performance feature, the ability to accelerate transaction commit times by orders of magnitude, when employing Storage Class Memory (NVDIMM- N nonvolatile storage) supported in Windows Server 2. This scenario is also referred to as “Persistent Log buffer” which is explained in detail in our SQL Server storage engine blog. Database Cloning – Clone database is a new DBCC command added that allows DBAs and support teams to troubleshoot existing production databases by cloning the schema and metadata, statistics without the data. Cloned databases is not meant to be used in production environments. To see if a database has been generated from a call to clonedatabase you can use the following command, select DATABASEPROPERTYEX(‘clonedb’, ‘is. Clone’). The return value of 1 is true, and 0 is false. In SQL Server 2. SP1, DBCC CLONEDATABASE added supports cloning of CLR, Filestream/Filetable, Hekaton and Query Store objects. DBCC CLONEDATABASE in SQL 2. SP1 gives you the ability to generate query store only, statistics only, or pure schema only clone without statistics or query store. A CLONED database always contains the schema and the default clone also contains the statistics and query store data. For more information refer KB 3. DBCC CLONEDATABASE (source_database_name, target_database_name) –– Default CLONE WITH SCHEMA, STATISTICS and QUERYSTORE metadata. DBCC CLONEDATABASE (source_database_name, target_database_name)WITH NO_STATISTICS –– SCHEMA AND QUERY STORE ONLY CLONEDBCC CLONEDATABASE (source_database_name, target_database_name)WITH NO_QUERYSTORE –– SCHEMA AND STATISTICS ONLY CLONEDBCC CLONEDATABASE (source_database_name, target_database_name)WITH NO_STATISTICS,NO_QUERYSTORE –– SCHEMA ONLY CLONECREATE OR ALTER (Yes, we heard you !!!) – New CREATE OR ALTER support makes it easier to modify and deploy objects like Stored Procedures, Triggers, User–Defined Functions, and Views. This was one of the highly requested features by developers and SQL Community. New USE HINT query option – A new query option, OPTION(USE HINT(‘< option> ’)), is added to alter query optimizer behavior using supported query level hints listed below. Nine different hints are supported to enable functionality which was previously only available via trace flags. Unlike QUERYTRACEON, the USE HINT option does not require sysadmin privileges. Programmatically identify LPIM to SQL serviceaccount – New sql_memory_model, sql_memory_model_desc columns in DMV sys. DBAs to programmatically identify if Lock Pages in Memory (LPIM) privilege is in effect at the service startup time. ![]() Programatically identify IFI privilege to SQL service account – New column instant_file_initialization_enabled in DMV sys. DBAs to programmatically identify if Instant File initialization (IFI) is in effect at the SQL Server service startup. Tempdb supportability – A new Errorlog message indicating the number of tempdb files and notifying different size/autogrowth of tempdb data files at server startup. Extended diagnostics in showplan XML – Showplan XML extended to support Memory grant warning, expose max memory enabled for the query, information about enabled trace flags, memory fractions for optimized nested loop joins, query CPU time, query elapsed time, top waits, and information about parameters data type. Lightweight per–operator query execution profiling – Dramatically reduces performance overhead of collecting per–operator query execution statistics such as actual number of rows. This feature can be enabled either using global startup TF 7. XE session containing query_thread_profile is enabled. When the lightweight profiling is on, the information in sys. Live Query Statistics feature in SSMS and populating a new DMF sys. New DMF sys. dm_exec_query_statistics_xml – Use this DMF to obtain actual query execution showplan XML (with actual number of rows) for a query which is still being executed in a given session (session id as input parameter). Microsoft SQL Server 2005 Compact Edition is the compact database for rapidly developing applications in both native and managed environment that extend. This article describes how to determine your current Microsoft SQL Server version number and the corresponding servicing or service pack level. Microsoft Visual Studio Express is a set of integrated development environments (IDEs) developed by Microsoft as a freeware and registerware function-limited version. The showplan with a snapshot of current execution statistics is returned when profiling infrastructure (legacy or lightweight) is on. New DMF for incremental statistics – New DMF sys. Better correlation between diagnostics XE and DMVs – Query_hash and query_plan_hash are used for identifying a query uniquely. DMV defines them as varbinary(8), while XEvent defines them as UINT6. Since SQL server does not have “unsigned bigint”, casting does not always work. This improvement introduces new XEvent action/filter columns equivalent to query_hash and query_plan_hash except they are defined as INT6. XE and DMVs. Better troubleshooting for query plans with push–down predicate – New Estimatedl. Rows. Read attribute added in showplan XML for better troubleshooting and diagnostics for query plans with push down predicates. Removing noisy Hekaton logging messages from Errorlog – With SQL 2. Hekaton engine started logging additional messages in SQL Errorlog for supportability and troubleshooting which was overwhelming and flooded the Errorlog with hekaton messages. Based on feedback from DBAs and SQL community, starting SQL 2. SP1, the Hekaton logging messages are reduced to minimal in Error log as shown below. Improved Always. On Latency Diagnostics – New XEvents and Perfmon diagnostics capability added to troubleshoot latency more efficiently. Manual Change Tracking Cleanup – New cleanup stored procedure sp_flush_CT_internal_table_on_demand introduced to clean the change tracking internal table on demand. For more information, refer KB 3. DROP TABLE support for replication – DROP TABLE DDL support for replication to allow replication articles to be dropped. For more information, refer KB 3. Signed Filestream Rs. Fx Driver on Windows Server 2. Windows 1. 0– The Filestream Rs. Fx driver introduced with SQL Server 2. SP1 is signed and certified using Windows Hardware Developer Center Dashboard portal (Dev Portal)allowing SQL Server 2. SP1 Filestream Rs. Fx driver to be installed on Windows Server 2. Windows 1. 0 without any issue. SQL Server 2. 00. R2 Requirements. SQL Server 2. R2 is Microsoft's premier enterprise data platform. In addition to its highly scalable relational database engine, SQL Server 2. R2 also provides industry- leading business intelligence (BI) capabilities with its SQL Server Integration Services (SSIS), SQL Server Analysis Services (SSAS), and SQL Server Reporting Services (SSRS) subsystems. If you're using one of the earlier editions of SQL Server or are considering moving from a competing database such as Oracle or DB2, then this article will help you choose the edition of SQL Server 2. R2 that's right for your organization. You'll learn about the features in the different editions of SQL Server 2. R2, as well as the hardware and software requirements for each edition. Related: Upgrading to SQL Server 2. R2 Common Hardware Requirements. The SQL Server relational database engine is designed to support both large enterprise databases and small- scale databases. As such, SQL Server 2. R2's hardware requirements are minimal. SQL Server 2. 00. R2 can run on both 3. Microsoft requires a minimum processor speed of 1. GHz but recommends systems with 2. GHz or faster. Almost all modern systems—even desktops and laptops—meet these requirements. In addition, Microsoft recommends that the server system support at least 8. Related: SQL Server 2. R2 New Features. The hard disk requirements vary according to the features installed. The following table lists the disk storage requirements for the main SQL Server features. SQL Server 2. 00. R2 Hard Disk Space Requirements Feature Disk Space Requirements Database Engine, Replication, and Full- Text Search 7. MB SSAS and data files 3. MB SSRS and Report Manager 3. MB SSIS 5. MB Client components (other than Books Online and SSIS tools) 1,8. MB SQL Server Books Online 1. MBSource: "Hardware and Software Requirements for Installing SQL Server 2. R1" Common Software Requirements. The different editions of SQL Server share several common software requirements. First, the SQL Server setup program requires Microsoft Windows Installer 4. All the x. 86 and x. SQL Server, except the SQL Server Express versions, require . NET Framework 3. 5 SP1. SQL Server 2. 00. R2 Express requires . NET Framework 2. 0. The IA- 6. 4 version also requires . NET Framework 2. 0. In addition, Microsoft Internet Explorer (IE) 6 SP1 or later is required. For client connectivity, SQL Server 2. R2 also requires the Shared Memory, Named Pipes, or TCP/IP network protocols. SQL Server Editions and Features. There are several different editions of SQL Server. Each edition is designed to meet a different level of requirements, and each edition has its own set of features and support for different operating systems. The following sections highlight the main features in each edition of SQL Server 2. R2, including the operating systems that are supported by each edition. SQL Server 2. 00. R2 Datacenter. SQL Server 2. R2 Datacenter provides the complete feature set available in SQL Server 2. The Datacenter edition provides the maximum scalability of the different SQL Server 2. R2 editions and is designed for the largest enterprise implementations that require maximum scalability. The Datacenter edition is priced at $5. Software Assurance (SA). The features available in SQL Server 2. R2 Datacenter include: Stream. Insight Premium real- time event processing Support for 3. Support for up to 2. CPUs Support for up to 2. TB of RAM (OS max) Database size 5. PB Support for 5. Hot- add CPU Hot- add RAM Database partitioning Database compression Transparent database encryption Resource Governor Partition table parallelism All database mirroring modes Failover clustering support for up to 1. Database snapshots Fast recovery Online indexing Online restore Distributed, partitioned views Parallel index operations Fine- grained auditing Oracle replication publishing P2. P transactional replication SSIS advanced transformations Change data capture (CDC) SSAS shared and scalable databases SSAS Star Join Query Optimization SSAS Proactive Caching SSAS partitioned cubes and distributed partitioned cubes SSAS writeback dimensions SSAS linked measures and dimension SSRS scale- out Web farms SSRS infinite click- through SSRS data- driving subscriptions Operating Systems Supported by IA- 6. Edition. Windows Server 2. R2 6. 4- bit Itanium. Windows Server 2. SP2 6. 4- bit Itanium. Windows Server 2. SP2 6. 4- bit Itanium Datacenter. Windows Server 2. SP2 6. 4- bit Itanium Enterprise. Windows Server 2. R2 SP2 6. 4- bit Itanium Datacenter. Windows Server 2. R2 SP2 6. 4- bit Itanium Enterprise Operating Systems Supported by x. Edition. Windows Server 2. SP2 6. 4- bit x. 64 Datacenter. Windows Server 2. SP2 6. 4- bit x. 64 Enterprise. Windows Server 2. SP2 6. 4- bit x. 64 Standard. Windows Server 2. R2 SP2 6. 4- bit x. Datacenter. Windows Server 2. R2 SP2 6. 4- bit x. Enterprise. Windows Server 2. R2 SP2 6. 4- bit x. Standard. Windows Server 2. SP2 6. 4- bit x. 64 Datacenter. Windows Server 2. SP2 6. 4- bit x. 64 Datacenter without Hyper- VWindows Server 2. SP2 6. 4- bit x. 64 Enterprise. Windows Server 2. SP2 6. 4- bit x. 64 Enterprise without Hyper- VWindows Server 2. SP2 6. 4- bit x. 64 Standard. Windows Server 2. SP2 6. 4- bit x. 64 Standard without Hyper- VWindows Server 2. SP2 6. 4- bit x. 64 Web. Windows Server 2. Windows Essential Server Solutions. Windows 2. 00. 8 R2 6. Datacenter. Windows 2. R2 6. 4- bit x. 64 Enterprise. Windows 2. 00. 8 R2 6. Standard. Windows 2. R2 6. 4- bit x. 64 Web Operating Systems Supported by x. Edition. Windows Server 2. SP2 Datacenter. Windows Server 2. SP2 Enterprise. Windows Server 2. SP2 Standard. Windows Server 2. SP2 6. 4- bit x. 64 Datacenter. Windows Server 2. SP2 6. 4- bit x. 64 Enterprise. Windows Server 2. SP2 6. 4- bit x. 64 Standard. Windows Server 2. R2 SP2 Datacenter. Windows Server 2. R2 SP2 Enterprise. Windows Server 2. R2 SP2 Standard. Windows Server 2. R2 SP2 6. 4- bit x. Datacenter. Windows Server 2. R2 SP2 6. 4- bit x. Enterprise. Windows Server 2. R2 SP2 6. 4- bit x. Standard. Windows Server 2. SP2 Datacenter. Windows Server 2. SP2 Datacenter without Hyper- VWindows Server 2. SP2 Enterprise. Windows Server 2. SP2 Enterprise without Hyper- VWindows Server 2. SP2 Standard. Windows Server 2. SP2 Standard without Hyper- VWindows Server 2. SP2 Web. Windows Server 2. SP2 x. 64 Datacenter. Windows Server 2. SP2 x. 64 Datacenter without Hyper- VWindows Server 2. SP2 x. 64 Enterprise. Windows Server 2. SP2 x. 64 Enterprise without Hyper- VWindows Server 2. SP2 x. 64 Standard. Windows Server 2. SP2 x. 64 Standard without Hyper- VWindows Server 2. SP2 x. 64 Web. Windows Server 2. R2 6. 4- bit x. 64 Datacenter. Windows Server 2. R2 6. 4- bit x. 64 Enterprise. Windows Server 2. R2 6. 4- bit x. 64 Standard. Windows Server 2. R2 6. 4- bit x. 64 Web. Windows Server 2. R2 x. 64 for Windows Essential Server Solutions SQL Server 2. R2 Enterprise. SQL Server 2. R2 Enterprise is designed for large, highly scalable enterprise implementations. IT provides support from almost all of SQL Server 2. R2's features except for Stream. Insight Premium. Notably, it provides support for all of the high- availability features. The Enterprise edition is priced at $2. SA) or $8,5. 92 per server ($2,1. SA), including 2. CALs. The features that are available in SQL Server 2. R2 Enterprise are: Support for 3. Support for up to eight physical CPUs Support for up to 2. TB of RAM Database size 5. PB Support for 5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |