In this tip I will demonstrate a simple way of launching a SQL Agent job when the job it depends on completes successfully.
The State of Database Monitoring survey is open. How are you currently monitoring your database estate? Are you working cross-platform? Tell us your opinions in our annual survey on the State of Database Monitoring for your chance to win a $500 Amazon voucher.
Take the survey.
Fingerprints provide some security, but a research suggests not necessarily much. Steve has a few thoughts.
No matter where you run your SQL Server® instances—on-premises, in a virtual machine, or in an Azure SQL Database Managed instance—the challenge is the same. How do you ensure you get optimum performance? Is the virtual machine impacting your database instance performance? Which queries cause the most blocking or deadlocking? Are you consuming more DTUs in your Azure SQL Database than you budgeted for?
Running software teams isn't as easy as it may seem, and the way you manage a startup is different than a mature organization. Steve has a few comments on the process one angel investor implements.
SQL Monitor 10.0.5 now supports a user role called "Reports user". A user added to this role, by an administrator, will be able to 'self-serve' SQL Monitor reports but won't be able to configure any other aspect of the monitoring service. Jeremiah Peschka explains how it works.
While Microsoft provides a number of different deployment options for its Azure SQL Database offerings, one in particular warrants special attention from the standpoint of its infrastructure dependencies: Azure SQL Database Managed Instance.
We have all heard migrating to the cloud can save you money and there are several ways moving your SQL Server workloads to the cloud can save your organization money. But, there are also missteps that can eat away at the savings, performance and even your availability creating instead an expensive, ineffective, difficult to manage cloud infrastructure.
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