SQL Server 2005 – Unattended installation – Part IV
In this section of this series, I am going to demonstrate how to install SQL Server 2005 Service Pack 1, to update the client components using command line options.
2006-07-20
1,239 reads
Administration
SQL Server 2005 - Unattended installation - Part III
In Part I and Part II of this series, we saw how to install the SQL Server 2005 Data Service component. In this section of this series, I am going to illustrate how to install SQL Server 2005 Database Services and SQL Server Analysis Services on a host machine using an .ini file.
2006-07-13
1,880 reads
SQL Server 2005 - Unattended installation - Part II
In this section of this series, I am going to illustrate how to install SQL Server 2000 Database Services on a server using various command line switches.
2006-07-12
1,946 reads
SQL Server and MOM Part II
This article will continue where the last one left off. We will import MOM 2005 Management Packs and Reports and begin monitoring SQL Server 2005.
2006-07-07
1,668 reads
SQL Server 2005's Undocumented Solution for Unattended Installs
Automating installations with SQL Server 2000 is easy because it creates a setup.iss file that you can use as input, but Microsoft removed this feature from SQL Server 2005. Learn an undocumented SQL Server 2005 feature that provides similar functionality to setup.iss.
2006-07-06
1,777 reads
Analyzing Disk Capacity for SQL Server
Ensuring that your disk subsystem performs well and does not run out of space is a balancing act that many DBAs learn over time through trial and "out of space" errors. New author Arindam Banerjee takes a look at some of the things to consider when capacity planning.
2006-07-04
15,932 reads
2006-06-30
1,443 reads
Using XP_EXECRESULTSET To Obtain Database Size Information and More
Have you ever used XP_RESULTSET in SQL Server? If you're like most DBAs, this procedure is rarely used and can be a little complicated to setup. New author J. T. Shyman brings us a look at just how useful this command can be in executing a command on every database.
2006-06-27
12,865 reads
Working with TempDB
This white paper describes how SQL Server 2005 uses tempdb. Many improvements in SQL Server 2005 optimize tempdb usage and make it easier to manage and to troubleshoot. A case study that uses a workload similar to TPC Benchmark H (TPC-H) shows new ways to manage and troubleshoot tempdb resources. This paper also includes items to consider when upgrading to SQL Server 2005 and configuring tempdb
2006-06-26
3,001 reads
Management Studio with SQL Server 2000
SQL Server 2005 has a new administrative tool called Management Studio, with many enhancements and changes from Enterprise Manager. But it's not just for SQL Server 2005 as new author Rob Farley shows us how to use this tool with SQL Server 2000.
2006-06-26
13,443 reads
Blogs
Advice I Like: Fear and Imagination
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
Cloud Data Driven User Group 2025 – Slides & Scripts
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
Leading Through Change: Guiding Teams in Times of Uncertainty
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Forums
Simple delete causes table scan on other tables with foreign key
Why is sql doing a full scan VS seeking on the index? I've included...
Show/Hide number of rows in table
We have a report that has multiple tables that list the top 15 performers...
Replication from IBMi DB2 to MS SQL
We have a tool called DB Moto that reads journals (like t-logs) and replicates...
Question of the Day
Checking Identities
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9
GO
DBCC CHECKIDENT(TravelLog, RESEED)
GO
INSERT dbo.TravelLog
(
CityID,
StartDate,
EndDate
)
VALUES
(4, '2025-09-14', '2025-09-17')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers