Powerchute 6.x User's Alert
If you run PowerChute 6.x on any of your servers, be very careful of patching and rebooting them. You might end up with more downtime and problems than you expected.
2005-08-18
4,366 reads
Articles
Business Intelligence with SQL Server Reporting Services - Part 2
A look at Parameterized reports, stored procedures to retrieve data and the Report Viewer.
2005-08-18
2,424 reads
Jacksonville - 2005 Code Camp
If you are near the Jacksonville, FL area on Saturday, August 27th, check out this code camp with our own Brian Knight. Get the chance to learn some great development from Brian and a few other experts.
2005-08-17
2,964 reads
The Basics of Cryptography Part 2
Encryption in SQL Server is difficult to implement and manage, but it is being required more and more often. However understanding what encryption means is as important as being able to manage and implement it. Michael Coles brings us part 2 in his series on explaining the mysteries behind cryptography.
2005-08-17
11,161 reads
Performance Monitoring by Internal Fragmentation Measurement
It has not been clear to what extent fragmentation, either internal or external, truly affects the performance of your SQL Server 2000 databases. New author Koby Biller discusses some of the impacts that it could have and has a free tool for download that can help you determine how fragmented your disk truly is.
2005-08-16
9,699 reads
Enabling Drillthrough in Analysis Services 2005
Discover the new Analysis Services 2005 drillthrough architecture. See how to set up drillthrough in Analysis Services 2005 and get guidance on migrating drillthrough settings from Analysis Services 2000 databases.
2005-08-16
1,966 reads
Single Point of Administration
Whether you write TSQL code or front end VB code against your SQL Server, it pays to have some good development practices that make your life easier. Jonathan Stokes has written a good article showing some of the good practices you should use.
2005-08-15
7,031 reads
Using TRY/CATCH to Resolve Deadlocks in SQL Server 2005
Deadlocks are unavoidable artifacts of today's RDBMS architecture–and all too common in high-volume OLTP environments. But thanks to .NET's Common Language Runtime (CLR), SQL Server 2005 provides developers with a new way to deal with error handling. In this month's column, Ron Talmage shows you how to harness TRY/CATCH to help resolve a deadlock.
2005-08-15
2,347 reads
Data Import Functionality Using SQL Server
Building robust functionality with maximum re-use of existing infrastructure and investment with little or no development is the goal for many businesses. This article is about using SQL Server DTS packages to achieve this goal. With minimum development, all the functionality required for data imports can be achieved with DTS programming in SQL Server.
2005-08-12 (first published: 2002-10-25)
92,488 reads
Controlling Transactions and Locks in SQL 2000 and 2005 - Part 1
A look at controlling transactions and locks with hints and snapshots in SQL Server 2000 and 2005.
2005-08-12
3,224 reads
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers