Find weak login passwords in your server
Use this script to search for SQL Server logins who use weak password
2010-01-05 (first published: 2009-12-16)
4,328 reads
Use this script to search for SQL Server logins who use weak password
2010-01-05 (first published: 2009-12-16)
4,328 reads
2009-12-16
3,088 reads
2009-12-15
3,629 reads
2009-12-14
3,919 reads
2009-12-11
4,067 reads
There are situations in which you need to individually handle each row in a result set. SQL Server 2008 provides a minimal set of tools — cursors and WHILE loops — to accomplish this task. I'll take a closer look at each option and explain why it's difficult to pinpoint which is better in terms of performance.
2009-12-11
4,754 reads
Learn how to use SQL Server Transact SQL with OPENROWSET and OPENQUERY commands to access and retrieve data from Active Directory.
2009-12-09
5,402 reads
2009-12-08
3,282 reads
Learn how to use common table expressions to simplify your code. Replace temp tables and correlated subqueries with this cool T-SQL feature.
2009-12-08
15,195 reads
2009-12-07
3,672 reads
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
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...
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