Dealing With Upper and Lower Case Data
Gregory Larsen demonstrates several examples of how to deal with different situations related to the case of character strings.
2007-02-16
2,757 reads
Gregory Larsen demonstrates several examples of how to deal with different situations related to the case of character strings.
2007-02-16
2,757 reads
Expanding on his series of string manipulation in T-SQL, Steve Jones takes a look at how you go about removing those unseen characters from your strings.
2008-02-04 (first published: 2007-02-13)
12,844 reads
In this session, Kathi continues her popular series and shows some of the more advanced joining techniques in T-SQL. She shows T-SQL self, outer and cross joins and gives many examples on how to use them.
2007-02-08
5,022 reads
The topic of cursors is the ultimate "hot potato" in the world of SQL Server. Everyone has a view on when they should and mainly should not be used. By example and testing Robyn Page proves that, when handled with care, cursors are not necessarily a "bad thing".
2007-02-06
2,669 reads
Most SQL Server DBAs have been taught that cursors are bad and should not be used. However there are some cases and places where they might be useful. SQL Server guru Andy Warren brings us an example of where they may be handy.
2008-01-03 (first published: 2007-01-15)
16,896 reads
Learn how to calculate days of the week based on the current date and how to calculate accounting months.
2007-01-12
3,468 reads
New to SQL Server 2005 is the PIVOT operator, which gives you the ability to rotate row level data into tabular data without the use of the CASE statement, as was necessary in previous versions of SQL Server.
2007-01-11
5,731 reads
Gregory Larsen discusses how to use the TOP clause to help solve requests where you want to restrict the number of records returned based on a record count.
2007-12-27 (first published: 2007-01-05)
8,395 reads
How often do you need to keep a total of all previous rows values when you run a query? This article shows you how you can achieve this.
2007-11-23 (first published: 2006-11-23)
7,074 reads
Data compression is a great method for maximizing data storage space and making data communication faster. However, compression and decompression of binary data sometimes can be quite tricky. Learn a few useful data-compression techniques.
2006-11-16
1,945 reads
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