2005-04-27
1,448 reads
2005-04-27
1,448 reads
A review of some other SQL Server 2005 graphical and command line programs, which should be part of the toolkit of every SQL Server 2005 database administrator and programmer.
2005-04-22
2,849 reads
Scripting out your SQL Server 2000 objects is useful in any number of ways. You can save off the scripts for version control, generate the scripts needed to migrate to new hardware or a new environment, or just package up your application for deployment. Jon Reade brings us a look at the SCPTXFR utility, which can prove very valuable in managing your scripts.
2006-10-13 (first published: 2005-04-14)
38,816 reads
This paper discusses the types of backups that are available in SQL Server 2000 and how backup functionality can be used in a disaster recovery plan. It includes general recommendations on how to improve backup and restore throughput and several case scenarios.
2005-04-14
3,974 reads
ADVERTISEMENT
So you've decided to secure your SQL Server infrastructure and you don't know where to start. This first guide in a two-part series on SQL Server patch deployment will help you track down those pesky servers before getting them properly patched.
SQL Servers represent a significant security challenge for a number of reasons. Primarily, they are ubiquitous. Hundreds of software packages use SQL Server as a data store as do a large number of commercial websites.
2005-04-11
2,667 reads
In working with many reporting tools over my career, particularly within enterprise business intelligence suites and high-end production reporting systems, I have become acquainted with various control features in each that allow administrators to govern the actions of end users. Reporting Services is no different in this aspect of need for control, and the application provides numerous avenues for restraining our users from kicking off resource crippling queries that, unchecked, could disrupt even the most robust systems, as well as to prevent other harmful activities. At various junctures within this series, we will examine ways to effect such controls on an intermittent basis.
2005-03-31
2,850 reads
SQL Server 2000 does an amazing job of running itself to a large extent, much more so in my experience, than the other major platforms. That being said, it isn't designed to run without some sort of DBA, at least not at an efficient level. But what value does a production level DBA bring to your organization? Your manager might wonder, but with many years of experience as a production DBA and manager, Steve Jones brings you a look at the value that a DBA provides.
2005-03-30
17,388 reads
2005-03-25
1,799 reads
SQL Server includes autonumber of identity columns despite the fact that they are not SQL-92 compliant. There is quite a bit of debate over the use of them in your database, but if you do decide to use them, you should be aware of potential problems. New author Troy Ketsdever brings us a story about his identity crisis and how it was solved.
2005-03-23
10,239 reads
2005-03-17
1,588 reads
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
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') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers