Guest columnist Robert Dorr explores how the reporting tool in SQL Server 2000 Service Pack 4 significantly reduces the time it takes to identify and determine the underlying causes of stalled and stuck I/O operations.
2005-05-13
2,764 reads
SQL Server delivers a number of functions for small to large organizations with needs ranging from internally developed applications to third-party off-the-shelf software. With all systems, data collection, entry and analysis at some level is required to meet organizational needs.
As user demands and the volume of data increase, it is imperative that all systems are properly configured and tuned based on the processing needs to meet the organizational requirements. This article will discuss two broad categories of SQL Server processing -- online transaction processing (OLTP) and data warehouses -- and will outline performance-tuning tips for each platform.
2005-05-13
2,165 reads
So far, in our series of articles, we have presented the most significant new and enhanced features available in Microsoft's SQL Server 2005 Beta 2, but neglected to provide you with information regarding its installation. While it is more than likely that, by now, you already have accomplished this entirely on your own, we suspect that you still should be able to benefit from a more in-depth analysis of the setup process. Explaining improvements in its design and implementation is the primary purpose of this article.
2005-05-12
2,407 reads
The solution described below should probably not be considered a "best practice" but it works. It came to life as I was pondering the following conundrum: How can I pass a little bit of data from an internal Access application behind a firewall out to a public web site in real time?
2005-05-11
3,113 reads
In my article last month, I wrote about different methods you could use to identify the state of a SQL Server Agent job. One of the methods I discussed was using the undocumented extended stored procedure (XP) "xp_sqlagent_enum_jobs." In this article, I will show you how to use the "xp_sqlagent_enum_jobs" XP to help identify long running jobs.
2005-05-10
2,117 reads
Backing up SQL Server data is like many of the things we do because we figure we need to. It is good for you, like eating a good diet and getting exercise. Unfortunately, folks are often about as successful with SQL Server backups as they are with diet and exercise.
This is the first in a series of articles covering SQL Server database backup. The series starts from the very basics of why database backup is important. The question of why to backup a database can inform many other decisions.
2005-05-09
2,411 reads
SQL Server Database administrators often copy(refer Fig 1.0) huge files, such as Full backup files and transaction log backup files from production to QA or from production to development environment and so on. Sometimes they need to copy source data files for importing. If they want to restore those Full backups or transaction log backup files or import those huge source files, they have to wait until the copy is complete.
2005-05-06
2,909 reads
Long anticipated, the arrival of radically restructured database architectures is now finally at hand. By Jim Gray of Microsoft Research.
2005-05-05
3,294 reads
Intrested in how to index XML documents? Here's a 12 page PDF on how this works.
2005-05-04
4,221 reads
A Feature comparison of Reporting Services for SQL 2000 and Crystal Reports / Crystal Enterprise. PDF file link.
2005-05-03
8,369 reads
By Arun Sirpal
Do you know what happens when you enable zonal redundancy for your SQL managed...
By Kevin3NF
Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting If you’ve...
By Steve Jones
The PASS Summit goes on tour this year, with the final date the first...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi I upgraded to new version of VS2019 to 16.11.49. My original SSIS package...
I've written this code, but it is showing right now as 2 rows per...
I have this table in SQL Server 2022:
CREATE TABLE CustomerLarge (CustomerID INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED , CustomerName VARCHAR(20) , CustomerContactFirstName VARCHAR(40) , CustomerContactLastName VARCHAR(40) , Address VARCHAR(20) , Address2 VARCHAR(20) , City VARCHAR(20) , CountryCode CHAR(3) , Postal VARCHAR(20) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers