SQL Server Index Maintenance Performance Tuning for Large Tables
This article describes a real-world example of performance tuning index maintenance for a large table of approximately 1 billion rows.
2011-05-26
5,252 reads
Additional Articles
TIME Gentlemen please! The SQL Server temporal datatypes
If you are still using the old Sybase DateTime datatype, it is a good idea to move your code to the more standard datatypes that were introduced in SQL Server 2008. Joe Celko explains why, and walks through some of the history of the TSQL way of storing and manipulating dates and times.
2011-05-25
3,801 reads
FILESTREAM Design and Implementation Considerations
This white paper is a companion to the information about FILESTREAM found on TechNet. This paper delves deeply into selected topics that should be considered when implementing a solution that uses FILESTREAM, including design considerations, maintenance, and management of a FILESTREAM environment.
2011-05-24
3,306 reads
PATINDEX Workbench
The PATINDEX function of SQL Server packs powerful magic, but it is easy to get it wrong. Phil Factor returns to the Workbench format to give a tutorial of examples, samples and cookbook ideas to demonstrate the ways that this underrated function can be of practical use. It is intended to be pasted into SSMS and used as a basis for experiment.
2011-05-23
5,331 reads
NewSQL: The Relational Model Meets Distributed Architectures
Research firm The 451 Group coins "NewSQL" to categorize a new breed of database designed for distributed environments -- like the cloud.
2011-05-20
4,064 reads
Scaling Up Your Data Warehouse with SQL Server 2008 R2
SQL Server 2008 introduced many new functional and performance improvements for data warehousing, and SQL Server 2008 R2 includes all these and more. This paper discusses how to use SQL Server 2008 R2 to get great performance as your data warehouse scales up. We present lessons learned during extensive internal data warehouse testing on a 64-core HP Integrity Superdome during the development of the SQL Server 2008 release, and via production experience with large-scale SQL Server customers. Our testing indicates that many customers can expect their performance to nearly double on the same hardware they are currently using, merely by upgrading to SQL Server 2008 R2 from SQL Server 2005 or earlier, and compressing their fact tables. We cover techniques to improve manageability and performance at high-scale, encompassing data loading (extract, transform, load), query processing, partitioning, index maintenance, indexed view (aggregate) management, and backup and restore.
2011-05-19
5,175 reads
Database Management for SharePoint 2010
With each revision, SharePoint becomes more a SQL Server Database application, with everything that implies for planning and deployment. There are advantages to this: SharePoint can make use of mirroring, data-compression and remote BLOB storage. It can employ advanced tools such as data file compression, and object-level restore. DBAs can employ familiar techniques to speed SharePoint applications. Bert explains the way that SharePoint and SQL Server interact.
2011-05-18
3,334 reads
SQL Server Replication: Providing High Availability using Database Mirroring
This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.
2011-05-17
3,504 reads
Space Impact of Replication Snapshot Agent Job in SQL Server
I have noticed that available disk space on my SQL Server is getting low and I see a number of files getting generated in the replication snapshot folder. Because of these files there is a space issue on my server. Why are these files here and what can I do to resolve this problem?
2011-05-16
2,739 reads
How to handle empty values in a line chart in SSRS
When continuous data is displayed on a chart, such as a line chart, data is displayed very smoothly. But when non-continuous data is displayed on such a chart, the chart behavior is different. The continuous data is displayed correctly, but the non-continuous data is ignored on the chart. In such cases, handling of empty points in the dataset is required to make the data continuous and displayed correctly on the chart. In this tip we will look at how to implement a solution for this problem.
2011-05-13
3,962 reads
Blogs
Advice I Like: Rewards from Work
By Steve Jones
The greatest rewards come from working on something that nobody has words for. If...
Overcoming Challenges: Navigating Common Pitfalls in FinOps Adoption
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Why your data still can’t answer a simple question
Every organization I talk to has the same problem dressed up in different clothes....
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
Creating a Simple and Flexible Random Password Generator in SQL Server
Comments posted to this topic are about the item Creating a Simple and Flexible...
Question of the Day
Identities and Sequences IV
When thinking about the identity property and sequence objects, which of these can be used with numeric and decimal data types?
See possible answers