Starting and Stopping SQL Server Part 4
Continuing with his series on working with SQL Server, Andy Warren looks at how long it can take to start or restart the services and why.
Using ITWIZ.EXE to Automate Index Analysis
This process uses ITWIZ.EXE the command line version of the Index Tuning Wizard. SQL trace file information is stored in a table on production then transferred to a non-production server. ITWIZ is then run against the transferred trace data resulting in a UNICODE SQL script. This script has index creation and deletion information as well as script parameters in a remarks section.
Male, Female and The Other One (NULL)
When programming in T-SQL, the impact of NULL values can be severe in many cases, especially aggregates. New Author Peter Ward brings us a great explanation on how NULLs can impact things like SUM operations.
How to Set Up a SQL Server Stress Test Environment in 8 Steps: Lessons
This article is the third in a series of four where I share my findings on baselining, monitoring, stress testing and performance tuning. It builds on the foundations of my previous articles on baselining and monitoring.
SQL Server 2005 Integration Services, Part 2: Developing Custom Compon
The first phase of Project REAL included the migration of existing SQL Server 2000 DTS packages to SQL Server 2005 Integration Services (SSIS) for a large electronic retailer. One source of information for the data warehouse was from TLog files, which contained data from point-of-sale cash registers in stores. TLog files store data in packed decimal format. To extract and transform this data into a format suitable for loading into the relational data warehouse tables, it was necessary to unpack and parse the files. To achieve this, custom pipeline components were implemented to read and transform the data by extending the SSIS object model. This paper discusses what we learned while implementing the pipeline components for extracting and parsing data from the TLog parser
Detecting Performance Issues With Sysprocesses
Analyzing and detecting performance problems is a big part of a DBA's job and also one of the more difficult ones to learn. New author Terry Troisi brings us a few things that you can use the next time your server spikes to 100% CPU.
Analysis Services 2005 protocol - XMLA over TCP/IP
It has been widely publicized that Analysis Services 2005 uses XML for Analysis 1.1 (XMLA) as its only network protocol for communication between client and server. XMLA is standard public protocol defined by XMLA council and full description can be found at www.xmla.org
Measuring SQL Performance
One thing that often amazes me is that many SQL Server developers do not actually measure the performance of their queries. Many of them thought that you needed external tools, more or less complicated, to run against your server, and they did not have the time or inclination to learn and try these. This article will describe a couple of much easier methods of measuring performance of queries.
Database Geek of the Week - Peter DeBetta
Peter runs DeBetta Software , a consulting firm that develops data-driven enterprise solutions. He is also a programming instructor for Wintellect, a training and consulting company, and a frequent speaker on SQL Server and other subjects.
Blogs
2025 Wrapped for Steve
By Steve Jones
I’ve often done some analysis of my year in different ways. Last year I...
The Book of Redgate: Spread across the world
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
Merry Christmas
By John
Today is Christmas and while I do not expect anybody to actual be reading...
Forums
SQL Server 2019 - Agent job PowerShell step issue
I have a couple of SQL Agent job steps which run PowerShell commands of...
Database security permissions save script
Comments posted to this topic are about the item Database security permissions save script
Database backup job steps
I have a SQL Agent job for backing up a set of Analysis Services...
Question of the Day
The Large Encoded Value
I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?
See possible answers