Easy or Hard
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
Using Script Task in SSIS to resolve problem of NULL values loaded from Excel.
If impeccable technical skills are a "given", what are the soft shills that will make you an Exceptional DBA rather than a competent DBA?
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
The DBA's Mantra: All data readers are evil. Steve Jones talks about a proposed corollary that might be appropriate to ensure security.
Greg Larsen looks at one way to design your database connection strategy to simplify changing application connections so you can plug-n-play databases with less administrative overhead when the need arises.
Along with some best practices, SQL Server MVP Hilary Cotter shares a log shipping setup process from start to finish.
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
How should we build tools? Should they be easy to use? Or does it make sense to have some things hard to do so that only experienced used choose them. Steve Jones comments on usability and the implications of your choices.
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...
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
We have a report that has multiple tables that list the top 15 performers...
We have a tool called DB Moto that reads journals (like t-logs) and replicates...
Comments posted to this topic are about the item Don't Forget About Financial Skills
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