IT solutions providers need to be able to discern between the different SQL Server 2008 R2 editions and pick the right one for a customer. These top 10 resources offer vital information on each of the four SQL Server 2008 R2 editions: Datacenter, Parallel Data Warehouse, Enterprise edition and Standard. Find out how you can use upgrade licenses for the new editions to create business opportunities.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You will also find out about the various SQL Server 2008 R2 requirements, including hardware, software and memory. See if your customer's environment meets the minimum SQL Server 2008 R2 requirements before recommending an upgrade.
- SQL Server 2008 R2 system requirements: Hardware and software (2,593)
Some SQL Server 2008 R2 system requirements are harder to understand than others so it's important for solution providers to recognize customer's individual OS needs. This tip details the hardware requirements that are consistent with all SQL Server 2008 R2 deployments, including a video card and monitor with a resolution of 1024 x 768 or above. You also need to find out SQL Server 2008 R2's memory requirements that vary by edition, such as the memory recommendation of 1 GB for SQL Server Express.
- New SQL Server 2008 R2 editions, features and licensing (1576)
Get information on each of the SQL Server 2008 R2 editions (Datacenter, Parallel Data Warehouse, Enterprise edition and Standard edition) and licensing in this tip. There are different management features and support for each edition, such as support for up to 256 logical processors in the SQL Server 2008 R2 Datacenter edition. Learn which of these editions best applies to your customer's needs and environment.
- Monitoring SQL Server 2008 R2 using SCOM 2007 R2 (1316)
Solution providers that want a stronger grip on customers' infrastructure and applications can employ System Center Operations Manager (SCOM) 2007 R2 when monitoring SQL Server 2008 R2. Keeping an eye on the health of your customer's SQL Server 2008 R2 and the amount of free space available within database and transaction log files is critical to ensuring the server is working properly. You can also use capacity information reports to get other pertinent information, such as SQL Server counters.
- Monitoring SQL Server 2008 R2 with SQL Server Management Packs (467)
If the idea of monitoring your customer's whole SQL Server 2008 R2 infrastructure seems like a lot to handle, SQL Server Management Packs (MPs) for SCOM 2007 R2 may be your answer. You can take advantage of the time saved by using the SQL Server MP for SCOM 2007 R2 to put time into daily activities. Read all the important information on the SQL Server MP to monitoring SQL Server 2008 R2 in this tip, including which SQL Server editions it supports and what it monitors, such as database status.
- Resource Governor in SQL Server 2008 R2 manages customers' workloads (368)
Managing workloads can be a burden for solution providers but they can use the SQL Server 2008 R2 Resource Governor to organize workloads and find out the amount of resources that each workload requires. Providers can also sell Resource Governor upgrade licenses, for example, to spark new business opportunities. Learn about the critical components of the Resource Governor, such as its classifier, as well as some limitations to be aware of, including resource exhaustion.
- Microsoft SQL Server 2008 R2: Adding CPU, memory on the fly (359)
In addition to workload management, the Microsoft SQL Server 2008 R2 Resource Governor can help providers with resource allocation for their customers. Providers can employ Resource Governor to define resource pools and add CPU and memory to prevent resource overconsumption. Take a look at the best way to use the Resource Governor and some potential drawbacks, such as the great volume of scripted required.
- Using Microsoft Upgrade Advisor for SQL Server 2008 R2 (174)
For a solution provider that is trying to perform a SQL Server upgrade for a customer, downtime is just about the last thing they need. Downtime can be prevented by using the Microsoft Upgrade Advisor for SQL Server 2008 R2, which contains two main components: the Analysis Services Wizard and the Report Viewer. Providers can follow the steps detailed in this tip to use each component properly. The first of the five steps for using the Analysis Services Wizard is identifying which of your customer's SQL Server components to analyze. The results are displayed on the Report Viewer.
- FAQ: Using Resource Governor in SQL Server 2008 R2 to allocate resources (82)
The SQL Server 2008 R2 Resource Governor is an important tool to allocate resources for your customer but you also need to know some of its limitations, such as being unable to limit resources that are consumed by other processes running on the server. This FAQ offers insight into what the Resource Governor can do for a solution provider, including resource pool creation, and how to use the Performance Monitor to determine if your customer's hardware resources are allocated correctly.
- Frequently Asked Questions: SQL Server 2008 R2
Browse through the most pressing questions surrounding SQL Server 2008 R2 and ensure you're up to date on new features, such as improved SQL Server Management Studio (SSMS) dashboards, and the Datacenter and Parallel Data Warehouse editions. Read about the role that PowerPivot plays in business intelligence (BI) for SQL Server 2008 R2 and some of the differences from SQL Server 2008, including an increase in the maximum number of logical processors supported to 64.
- Microsoft SQL Server 2008 R2 spotlight
This Microsoft SQL Server 2008 R2 spotlight focuses on the new aspects of SQL Server 2008 R2 that are important to providers. Get in-depth analysis on the new Datacenter and Parallel Data Warehouse editions, and learn what Microsoft has done to improve BI. This tip also covers the other factors to consider when discussing a potential upgrade with a customer, such as migration costs and hardware and memory requirements.