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
Additional Articles
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
Top 10 SQL Server Counters for Monitoring SQL Server Performance
Greg Larsen lists his top 10 SQL Server counters for maintaining database performance.
2011-05-12
7,210 reads
Find SQL Server data and log files that are almost out of space
On many SQL Servers database file size, either data or log, may be restricted to a maximum size to ensure there is adequate space on the server. The problem with this is that if your data or log file runs out of space you will get an error message
2011-05-11
4,028 reads
Using SQL Server Resource Governor to Control Resource Utilization
This article introduces SQL Server Resource Governor and provides a detailed walkthrough of using Resource Governor to manage the resource utilization of SQL Server.
2011-05-10
3,225 reads
Find SQL Server databases where log file is too large
I support thousands of databases and I'm running across situations where I have a database that has a data file of a couple hundred megabytes and the associated log file is gigabytes in size! I understand this is because I may not have my transaction log backups scheduled properly. What I'm interested in is an easy way to identify these situations where the SQL log file is too large, so I can go in and further analyze these problem databases without needing to look at each database.
2011-05-09
5,073 reads
Blogs
Who’s the Winningest Coach (with AI Help)
By Steve Jones
I was listening to the radio the other day and the hosts were discussing...
Learning from Mistakes: T-SQL Tuesday #194
By Steve Jones
We’re a week late, once again my fault. I was still coming out of...
Stupid Things I Did With AI: ASCII Art
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
Forums
MBOX Email Conversion for Backup: Which Format Is Best?
I have several important email accounts stored in MBOX format from clients like Thunderbird...
Basic Always On Groups Randomly Stop Synchronizing
In one of my environments I have 3 pairs of Always On SQL 2022...
Learning From Breakage
Comments posted to this topic are about the item Learning From Breakage
Question of the Day
Adding and Dropping Columns I
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ) ON [PRIMARY] GOI decide to add two new columns for the StateProvince and Country. What code should I use? See possible answers