Articles

Technical Article

Support for 15,000 Partitions in SQL Server 2008 SP2 and SQL Server 2008 R2 SP1

In SQL Server 2008 and SQL Server 2008 R2, the number of partitions on tables and indexes is limited to 1,000. This paper discusses how SQL Server 2008 SP2 and SQL Server 2008 R2 SP1 address this limitation by providing an option to increase the limit to 15,000 partitions. It describes how support for 15,000 partitions can be enabled and disabled on a database. It also talks about performance characteristics, certain limitations associated with this support, known issues, and their workarounds. This support is targeted to enterprise customers and ISVs with large-scale decision support or data warehouse requirements.

2011-06-09

2,755 reads

External Article

REAL PRACTICES: Performance Scaling Microsoft SQL Server 2008 Analysis Services at Microsoft adCenter

This white paper explains how Microsoft® adCenter implemented a Microsoft SQL Server® 2008 Analysis Services Scalable Shared Database on EMC® Symmetrix VMAX™ storage. Leveraging TimeFinder® clones and Enterprise Flash Drives with the read-only feature of SQL Server 2008 Analysis Services allowed adCenter to dramatically scale out OLAP while maintaining SLAs and decreasing system outages.

2011-06-08

2,675 reads

External Article

Using PowerShell to Manage SQL Server

The purpose of this article is to demonstrate a custom scripting framework which enables the management of SQLServer databases from a Windows PowerShell session and also to extend Powershell’s flexibility by creating a set of commands customized to our needs. I will call this framework comprised of a library of modules and functions specialized to manage SQLServer the DBA profile.

2011-06-06

3,307 reads

External Article

SQL Server Agent Jobs without an Operator

I work in a fairly large and unwieldy SQL Server shop. Our environment is the wild west. I have DBAs and Developers on my team that create SQL Server Agent Jobs all of the time and there is never an operator setup to email anyone based on a failure condition. I know the right solution here is to "tame the wild west" by locking down the environment and setting up a change management process, but I think that is a topic for another day. Can you give me some idea of how to identify the new recently created SQL Server Agent Jobs and Jobs without an operator setup to email us for a failure condition? I would like to receive emails when either of these conditions occur. Check out the solution to this tip to learn how.

2011-06-03

4,386 reads

Blogs

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

A New Word: Dolorblindness

By

dolorblindness – n. the frustration that you’ll never be able to understand another person’s...

Claude Code Helps Analyze Test Data Manager Log Files

By

I had a customer ask about analyzing their Test Data Manager (TDM) usage to...

Read the latest Blogs

Forums

Data Warehouse Toolkit meets Star Schema: The Complete Reference

By pietlinden

Is there a good syllabus for reading these two together? (Yes, it's called the...

GPX distance and time analysis in SQL Server

By Cláudio Tereso

Comments posted to this topic are about the item GPX distance and time analysis...

The DBA is Dead; Long Live the DBA

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The DBA is Dead; Long...

Visit the forum

Question of the Day

Changing the AG Listener

In SQL Server 2025, if I want to remove an IP from a listener, what do I do?

See possible answers