블로그 이미지
LifeisSimple

calendar

1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30

Notice

2012. 1. 19. 14:55 Brain Trainning/DataBase

링크  http://www.microsoft.com/sqlserver/en/us/product-info/compare.aspx 

Compare Microsoft SQL Server Editions

Share this page

Compare Database Solutions

Provide your organization with the foundation for a comprehensive information platform that helps you get the most value out of your database environment by using Microsoft SQL Server 2008 R2. Plus, you get a range of editions with new features to choose from to meet the needs of organizations both large and small, including new premium editions for large-scale data centers and data warehouses. SQL Server 2008 R2 further enhances your scalability potential by supporting up to 256 logical processors.

Compare SQL Server 2008 R2 with competitive database solutions. You can also compare different editions of SQL Server 2008 R2 by capability or learn more about all editions.

posted by LifeisSimple
2011. 1. 13. 11:01 Brain Trainning/DataBase
SP2를 적용하기 전에 우선 어떤것들이 개선되고 버그가 픽스됬는지 확인

패치는 다음과 같이 합니다. 

Apply a service pack or patch SQL Server 2008 in a clustered environment 
    Step 1 : Validation wizard 
    Step 2 : Pre-check
    Step 3 : Installation of the first node
    Step 4 : Add a new node 
    Step 5: Apply a service pack or hotfix on a SQL cluster 

Installing Service Pack SQL Server 2008 in failover cluster is very different than the SQL Server 2005 cluster failover.

With SQL Server 2005, when you start installing cluster service pack (or hotfix), it must be launched on the active node (node that hosts the instance). When installing the Setup will launch simultaneously  "remote silence" on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.

With SQL Server 2008, to reduce the downtime, we have revised the method of deployment. Now if you want to apply a service pack (or hotfix), you must install in first on the passive nodes. The passive nodes are updated before the active node.

Therefore, for your instance SQL Server 2008  in failover cluster, you must follow the scenario below for the application of Service Pack, Cumulative Update or Hotfix :

1.  Apply the hotfix on pasive node N2
2.  Reboot the passive node N2
3.  Failover on SQL resource : the passive node become the active node
4.  Apply the hotfix on the passive node N1
5.  Reboot the passive node N1

You can check the version of SQL server with the following query:

SELECT   

      SERVERPROPERTY('IsClustered') as _1_Means_Clustered ,   
      
SERVERPROPERTY('Edition') as Edition ,   
      
SERVERPROPERTY('ProductVersion') as Version  , 
      
      
SERVERPROPERTY('ComputerNamePhysicalNetBIOS') as ActiveNode
 


이건 개선된 기능 및 다운로드 링크

Overview


Microsoft SQL Server 2008 Service Pack 2 (SP2) is now available for download. These packages may be used to upgrade any edition of SQL Server 2008. We remain committed to providing our customers with essential changes via Service packs. Service Pack 2 contains updates for SQL Server Utility, Data-Tier Application (DAC), as well as integration capability for Microsoft Reporting Services with the Microsoft SharePoint 2010 Technologies. Service Pack 2 introduces support for a maximum of 15,000 partitions in a database, and includes SQL Server 2008 SP1 Cumulative Update 1 to 8.  While keeping product changes contained, we have made significant investments to ease deployment and management of Service Packs. Microsoft SQL Server 2008 Service Pack 1 is not a prerequisite for installing SQL Server 2008 Service Pack 2. 

For more information about SQL Server 2008 Service Pack 2, please visit our Release Notes

What's New:
  • Reporting Services in SharePoint Integrated Mode. SQL Server 2008 SP2 provides updates for Reporting Services integration with SharePoint products. SQL Server 2008 SP2 report servers can integrate with SharePoint 2010 products. SQL Server 2008 SP2 also provides a new add-in to support the integration of SQL Server 2008 R2 report servers with SharePoint 2007 products. For more information see the “What’s New in SharePoint Integration and SQL Server 2008 Service Pack 2 (SP2)” section in What's New (Reporting Services).
  • SQL Server 2008 R2 Application and Multi-Server Management Compatibility with SQL Server 2008.
    • SQL Server 2008 Instance Management.With SP2 applied, an instance of the SQL Server 2008 Database Engine can be enrolled with a SQL Server 2008 R2 Utility Control Point as a managed instance of SQL Server. For more information, seeOverview of SQL Server Utility in SQL Server 2008 R2 Books Online.
    • Data-tier Application (DAC) Support.Instances of the SQL Server 2008 Database Engine support all DAC operations delivered in SQL Server 2008 R2 after SP2 has been applied. You can deploy, upgrade, register, extract, and delete DACs. SP2 does not upgrade the SQL Server 2008 client tools to support DACs. You must use the SQL Server 2008 R2 client tools, such as SQL Server Management Studio, to perform DAC operations. A data-tier application is an entity that contains all of the database objects and instance objects used by an application. A DAC provides a single unit for authoring, deploying, and managing the data-tier objects. For more information, see Designing and Implementing Data-tier Applications.

Please Note:  SQL Server 2008 SP2 applies only to the SQL Server 2008 release.  This service pack can not be applied on top of SQL Server 2008 R2.


이건 픽스된 버그 : http://support.microsoft.com/kb/2285068

List of the bugs that are fixed in SQL Server 2008 Service Pack 2

On This Page

INTRODUCTION

This article lists the bugs that are fixed in Microsoft SQL Server 2008 Service Pack 2 (SP2).

Notes
  • Other fixes that are not documented may be included in the service pack.
  • This list will be updated when more articles are released.
For more information about how to obtain SQL Server 2008 service packs, click the following article number to view the article in the Microsoft Knowledge Base:
968382  How to obtain the latest service pack for SQL Server 2008

MORE INFORMATION

In addition to the fixes that are listed in this article, SQL Server 2008 SP2 contains the hotfixes that were included in Cumulative Update 1 through Cumulative Update 8 for SQL Server 2008 Service Pack 1 (SP1). For more information about the cumulative update packages that are available for SQL Server 2008 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 SP1 was released 

The bugs that are fixed in this service pack

For more information about the bugs that are fixed in SQL Server 2008 SP2, click the following article numbers to view the articles in the Microsoft Knowledge Base.
VSTS bug numberKB article numberDescription
249682 2216454  FIX: Error message when you run the ProcessAdd command after you make changes to the partition on a server that is running SQL Server 2008: "Internal Error: An unexpected exception occurred"
256736 2322209  FIX: Incorrect results if you use parentheses around SELECT in a statement that has a common table expression in SQL Server 2008
258076 2216456  FIX: SQL Server 2008 Service Pack 2 enhancements to the “Operation has been cancelled” error message text in Analysis Services
270561 2216460  Error message when you try to open a project in SQL Server 2008: "The located assembly's manifest definition does not match the assembly reference"
274280 2216461  SQL Server 2008 setup fails to install on a Windows Server 2008-based cluster mount point
284360 955850  Error message when you try to use the binaries from the SQL Server System CLR Types package (SQLSysClrTypes.msi): "Unable to load DLL 'SqlServerSpatial.dll': This application has failed to start because the application configuration is incorrect"
301603 2216465  Slipstream installation of SQL Server 2008 fails if the /PCUSOURCE or /CUSOURCE has a space in the path
317800 2216472  A SQL Server 2005 Analysis Services drillthrough statement result is empty
340066 2216474  FIX: You may experience some loss of data when you use an UPDATE statement with a SET clause that uses the time, datetime2 and datetimeoffset types in SQL Server 2008
347731 2216478  Error message when you run Get-Command in a PowerShell version 2 environment on a server that is running SQL Server 2008: "Object reference not set to an instance of an object"
351286 2216480  FIX: The margins are not retained in a report when the report is exported to Excel on a server that is running SQL Server 2008, and then you preview the report in Excel
351981 2216484  FIX: Error message when you export a report to Excel in Report Manager on a server that is running SQL Server 2008: "Unhandled managed exception: Type = System.ArgumentOutOfRangeException"
357416 2216485  FIX: Resource Monitor enters a non-yielding condition on a SQL Server 2008 server
390126 2216491  The SQL Dumper utility cannot generate error dump files on a SQL Server 2008 failover cluster on an Advanced/Enterprise Failover Cluster install
396527 980671  Correcting the lack of cryptographic salt variation on SQL Server sa login hash
402453 2019402  No mapping between account names and security IDs was done" error when adding a node to a SQL Server 2008 Failover Cluster
426753 2216499  You cannot enroll a SQL Server 2008 database instance into a SQL Server Utility
426753 2253128  You cannot deploy a Data-Tier application to a SQL Server 2008 database instance
427703 2216501  FIX: Multiserver jobs are not downloaded from a SQL Server 2000 in the MSX role on to a SQL Server 2008 in the TSX role
256736 2322209  FIX: Incorrect results if you use parentheses around SELECT in a statement that has a common table expression in SQL Server 2008
524642 2283072  FIX: A hotfix is available that enables SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key for FIPS compliancy
370540 2448971  FIX:The locks of a table are not escalated when you insert many rows into a table in SQL Server 2008

Additional issues that are fixed in this service pack

Resolutions to the following issues are also included in SQL Server 2008 SP2.
VSTS bug numberDescription
270934 DBCC corruption errors occur during SQL Server 2008 collations when strings that have Jamo sequences that follow the Japanese prolonged sign are used.
271554 FIX: The syscolpars system base table displayed duplicate rows. This fix distinguishes them by adding the procedure number in DBCC checkcatalog.
271708 When query has a filter that references a column in the sys.dm_server_audit_status view, the filter is ignored, and all the rows are returned from sys.dm_server_audit_status.
280004 The asynchronous bucketing target shows incorrect value/string pairs for mapped fields when compared to the information that is available in dm_xe_map_values.
284760 FIX: The Mismatched view can contain multiple views that have different numbers of indexes. This fix forces a deterministic order of views to compare, based on matched functions and on the number of matched indexes.
285377 Users receive an "Access Denied" error message when they navigate to Report Manager locally if UAC is enabled. Adding an updated "Access Denied" message to mention UAC could allow users to address the setting accordingly.
291707 In a given database, using a server cursor that is declared for a select statement that contains any system view may give incorrect results after that database is attached and reattached.
293089 Radial Gauge users who try to use “RateOfChange” or “Integral” as the formula type for the MaximumValue or MinimumValue on the gauge do not see a value in the property grid dropdown list.
296314 FIX: The FailoverAnalysis.sql file is installed during a SQL Server Failover Cluster setup. This script will be called automatically when failure occurs. The SqlDMVScriptTimeout private property controls for how many milliseconds the script can take to finish.
302563 Users receive a validation error when they are upgrading Shared Data Sources that have a space in the name. The error indicates that the name cannot contain spaces.
302707 Installation of Service Pack 1 for SQL Server Business Intelligence Development Studio 2008 fails because of a missing configuration file.
304390 The ring buffer displays incomplete event data (events output from dm_xe_session_targets) when it reaches the size limit for the XML output.
307313 Users cannot return multiple cookies in their HTTP module. This affect users when they try implement custom authentication.
309869 The sqlsos.task_address, sqlsos.worker_address, and sqlsos.scheduler_address Extended Events actions display an incorrect address.
310483 Reporting Services 2008 Designer converts centimeters to inches in the Tablix. This causes a loss of layout precision.
313780 Uninstalling the first of two named AS instances disables the SQL Browser. This causes the second named instance to be unreachable.
319216 Users cannot use stored credentials in their data sources if a Smart Card is required.
322046 A query that has a subselect clause that uses a set expression that does not return any calculated members returns an error saying that subselects that have calculated members are not allowed.
327301 In Analysis Services, setting a dimension default member by using an MDX expression that has a NonEmpty function causes the server to return an internal error when it tries to open the cube.
328752 The sys.dm_os_wait_stats view displays duplicate rows for the MISCELLANEOUS wait type. This can cause problems for monitoring tools.
331630 Integer value gets incorrectly rounded in the SQL Server Reporting Services Reusable Query Designer.
333544 FIX: A new error code (6257) is returned when a user tries to register a CLR assembly that is built against a newer runtime, such as CLR v4. The previous error message (code 6218) was confusing and did not state the actual issue. See the bug for details.
336809 An edge case inserts an identity value outside the current range in "set identity_insert TABLE_NAME on" mode. This issue also occurs in backup/restore operations.
338247 If parameters that are bound by the SQLBindParameter function specify a length of SQL_DATA_AT_EXEC, the SQL Server 2008 Native Client ODC driver causes an access violation if the SQLPutData function specifies a length of SQL_NULL_DATA when the parameter value is supplied for execution.
338999 SQL Server Reporting Services 2008 experiences a connection leak when a user uses the SOAP interface to run and export a report.
347779 SQL Server sometimes generates a "There is insufficient system memory in resource pool 'internal' to run this query" error message. This situation is often preventable.
350670 Users receive a "Page Expired" error message when they try to refersh a rendered report after the report remains idle for one hour.
352788 Error 955 occurs when users tried to configure Management Data Warehouse if they have databases on their server that are not online.
352862 ReportBuilder 2.0 ClickOnce displays a blank report at startup if a user edits the report by using ReportBuilder 2.0 from a SharePoint 12 website.
355222 If MARS is used, the sys.dm_os_tasks view displays the same value in the request_id column for all tasks instead of reporting the correct value associated with each task.
355228 FIX: A new error message indicates the cause of an access violation that occurs if the bucketizer target parameters are set incorrectly.
356127 Incorrect column collation information is returned when BCP.exe retrieves column metadata information.
360584 Subscriptions fail during execution because of an in-memory data structure problem during the attempted email delivery of an MHTLML-rendered report.
368388 BIDS 2008 Report Designer running together with SQL Server Reporting Services 2008 crashes when users resize a table row.
376257 The TO, CC, and BCC fields of the "Report Delivery Options" dialog box are cleared after users cancel or close the "Schedule Details" dialog box to return to "Report Delivery Options."
383747 Collection sets work incorrectly when they collecting performance counters on a cluster if the SQL instance name is the same as the virtual network name.
384800 FIX: Improved and additional information is logged for InvalidReportParameterException in Verbose output if certain conditions occur during parameter processing.
393410 When users clear the selection of one or more months in a monthly schedule, SSRS creates separate schedules for each month that is still selecteded. In some cases, this can cause an "@active_end_date cannot be before @active_start_date" error.
393879 Data-Driven subscription fails if a NULL value is returned when it is mapped to the report parameter, which accepts a NULL value.
394977 Subscription and Delivery issues are difficult to diagnose in the Reporting Services trace file. More verbose logging is required.
415084 Users receive an "Index was out of range. Must be non-negative and less than the size of the collection" error message when they export to PDF.
419740 Users cannot use custom authentication in the SQL Server 2008 Web SKU.
424595 If a user creates a user-defined type and a table valued function in the same transaction, and if the function has a return table containing a column of the user-defined type, a self-deadlock occurs. Additionally, the connection that tries to perform these operations is terminated.
421922 FIX: Support is provided for a maximum of 15,000 partitions in tables and in indexes in the Enterprise, Developer, and Evaluation editions of Microsoft SQL Server 2008 SP2. For more information about how this support can be enabled and disabled, about its limitations, and about some known issues and workarounds, see the "Support for 15,000 Partitions" white paper (http://go.microsoft.com/fwlink/?LinkId=199773).
424804 In Analysis Services, some customers may experience access violation when they use a parent-child hierarchy in the condition of an IIF function.
426631 Using a PeriodsToDate function that has a Null member parameter may cause an "Unexpected exception" error.
429253 An incorrect version number is displayed in SQL Server Management Studio and in SQL Server Reporting Services. This causes confusion because the displayed number does not vary from the RTM version number after an upgrade is performed.
430703 A secondary exception may occur when Analysis Services generates a Watson dump. This is true whether the Watson dump is generated because of an actual exception or because of an explicit request to dump on certain errors. If the secondary exception occurs, the server can experience infinite recursion. This generates many dumps, and then shuts down the server.
431298 FIX: In SSRS 2008 Service Pack 2, the RS add-in for SharePoint 2007 for communicating with SSRS 2008 R2 report server is updated. This enables access to certain functionality in ReportBuilder 3.0, ReportParts, and ATOM Renderer, including the new Report preview in ReportBuilder 3.0.
431301 Processing objects in a database that contains thousands of metadata objects takes a long time to begin importing the data. This occurs because the server has to build a job schedule before the data import begins. Additionally, the algorithm that is used to determine dependencies causes slow performance when many metadata objects exist in the database.
432094 A spatial index cannot be safely created in a table that uses CELL_ID, CELL_ATTRIBUTES or SRID for column names.
448007 In certain conditions, the partitioned column name in error message 11405 may be wrong. This causes an incorrect column name to be printed.
455538 Using cell security together with calculations yields incorrect results when a NON EMPTY clause is used.
456534 Read access violation occurs during a commit process if two transactions run simultaneously: one to modify or create a partition, and one to process a dimension.
471363 When Microsoft Office 12 is integrated with SQL Server 2008 Reporting Services, the SharePoint integration does not default to the Report Builder clickonce URL, preventing Report Builder from starting.
471421 FIX: Localization issue in the Turkish SKU: bread crumbs are now localized on new reportpart library pages.
499162 FIX: An accessibility issue that occurs because the MSAA name of "Symbol" is null. MSAA names are updated and are now discoverable.
503096 FIX: Improved the performance of index creation by DDL statements for tables that have many partitions and that contain no data. Previously, the time required for this process increased in a geometric progression as the number of partitions increased. The time required now increases in a linear progression.
515240 Using table valued parameters for LOB columns may cause an access violation on the server.
520700 MSAA names for the Radial Scale Properties dialog box are incorrect and are not accessibility compliant.
525601 During a check for a granular audit, the algorithm that is used to list any audits that include the event may experience memory leaks of the list of audits. This continues until out-of-memory errors occur and the service has to be restarted to reclaim the memory.

Note If you are upgrading from SQL Server 2008 SP1Cumulative Update 9 or a later version, you must apply a post-SQL Server 2008 SP2 cumulative update after you upgrade to SQL Server 2008 SP2 to obtain all the fixes. 

For more information about the post-SQL Server 2008 SP2 Cumulative Update, click the following article number to view the article in the Microsoft Knowledge Base:
2289254 Cumulative update package 1 for SQL Server 2008 Service Pack 2

REFERENCES

For more information about how to determine the current SQL Server version and edition, click the following article number to view the article in the Microsoft Knowledge Base:
321185  How to identify your SQL Server version and edition
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

APPLIES TO
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2285068
posted by LifeisSimple
2010. 10. 4. 00:00 Brain Trainning/DataBase
SQL Server 2008 SP2가 나왔습니다. 

지금 적용을 하면 마루타가 될까요? ㅎㅎㅎ

적용 방법은 요렇게...  (2005 와 2008은 패치 방법이 다릅니다.)

Apply a service pack or patch SQL Server 2008 in a clustered environment 
    Step 1 : Validation wizard 
    Step 2 : Pre-check
    Step 3 : Installation of the first node
    Step 4 : Add a new node 
    Step 5: Apply a service pack or hotfix on a SQL cluster 

Installing Service Pack SQL Server 2008 in failover cluster is very different than the SQL Server 2005 cluster failover.

With SQL Server 2005, when you start installing cluster service pack (or hotfix), it must be launched on the active node (node that hosts the instance). When installing the Setup will launch simultaneously  "remote silence" on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.

With SQL Server 2008, to reduce the downtime, we have revised the method of deployment. Now if you want to apply a service pack (or hotfix), you must install in first on the passive nodes. The passive nodes are updated before the active node.

Therefore, for your instance SQL Server 2008  in failover cluster, you must follow the scenario below for the application of Service Pack, Cumulative Update or Hotfix :

1.  Apply the hotfix on pasive node N2
2.  Reboot the passive node N2
3.  Failover on SQL resource : the passive node become the active node
4.  Apply the hotfix on the passive node N1
5.  Reboot the passive node N1

You can check the version of SQL server with the following query:

SELECT   

      SERVERPROPERTY('IsClustered') as _1_Means_Clustered ,   
      
SERVERPROPERTY('Edition') as Edition ,   
      
SERVERPROPERTY('ProductVersion') as Version  , 
      
      
SERVERPROPERTY('ComputerNamePhysicalNetBIOS') as ActiveNode


한글 링크는 아래에 


영문버전 링크

Files in this Download


The links in this section correspond to separate files available in this download. Download the files most appropriate for you.

File Name:
Size:
Download files below
Microsoft SQL Server 2008 SP2 Readme.htm
16KB
SQLServer2008SP2-KB2285068-IA64-ENU.exe
343.4MB
SQLServer2008SP2-KB2285068-x64-ENU.exe
349.8MB
SQLServer2008SP2-KB2285068-x86-ENU.exe
284.8MB

Quick Details


Version:
10.00.4000.00
Date Published:
9/29/2010
Change Language:
Knowledge Base (KB) Articles:

'Brain Trainning > DataBase' 카테고리의 다른 글

MNG : Backup 유지관리계획  (0) 2010.10.17
SQL Diag 이렇게 이용  (0) 2010.10.16
MySQL Clustering Config  (0) 2010.09.29
MySQL Clustering on Ubuntu  (0) 2010.09.29
MySQL Cluster 구성  (0) 2010.09.20
posted by LifeisSimple
prev 1 next