The Face of BI for SQL Server
Donald Farmer recently left Microsoft, and he will be missed, but Steve Jones knows that there will be new faces to get to know.
2011-01-20
197 reads
Editorial
Skunk Works
The idea of a skunk works is to build a project that works under the radar, by a small and loosely organized group of people. Used to fuel innovation, this is an idea that you might apply to SQL Server BI projects.
2011-01-19
170 reads
Data Scientists
Would you want to be a data scientist? Are you one now? Steve Jones talks about this skill that we might appreciate in our daily work.
2011-01-18
420 reads
The Spring Semester
SQL University is kicking off their spring semester, and Steve Jones is looking to motivate you to participate.
2011-01-17
73 reads
ETL Security Holes
The growth of ETL processes and secondary systems for reporting, decision support and other analysis creates an issue. Steve Jones points out that we ought to be remembering that security needs to be applied to data, not just systems.
2011-01-17
234 reads
Scaling Up
Would you want to manage a VLDB? Or write the code for an application that uses one? This Friday Steve Jones asks the question of you.
2011-01-14
139 reads
Operating in Failure
Today we have an editorial from Sept 25, 2005 being republished as Steve is on vacation. This one talks about the need to expect failure in our systems and code for it.
2011-01-13
72 reads
The Importance of My Cloud Data
Steve Jones likes the cloud, but doesn't necessarily trust it. After a recent Hotmail outage, he outlines a potential issue that he sees with cloud computing.
2011-01-12
171 reads
NoSQL Basics
Today Steve Jones talks about NOSQL and why it might be important for SQL Server DBAs to understand more about it and be able to talk about when it is appropriate to use.
2011-01-11
699 reads
Building Better Communication Skills
Today Steve Jones reminds us that our communication skills are important. They are something that we use constantly at work and are worth developing.
2015-12-08 (first published: 2011-01-10)
428 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