SQL Saturday #33
A one day training event in the Charlotte, NC area. Come join MVPs from around the area at another great SQL Saturday.
A one day training event in the Charlotte, NC area. Come join MVPs from around the area at another great SQL Saturday.
When getting help online, you need to be professional and a part of that is being responsible. Steve Jones reminds us today that we have to be careful about what we post.
Another sample chapter from Wiley, this time for one of the hot topics in business intelligence: data mining.
The article will provide an overview of Master Data Services and a sample SSIS Package.
XQuery and SQL/XML standard are processors for XML. SQL/XML was designed to try to match the capabilities of XQuery as closely as possible and XQuery was designed not only to support XML, but also to support relational processing. Read on to learn why this may have a negative influence on their capabilities.
Do you put an identity column on every table? That might be a bad habit you want to kick, but not all at once. Steve Jones comments on this common data modeling practice.
Seth Delconte brings us a technique to solve a common request. Using the NEWID function to return a random record from a result set.
This past week's news had a lot of news about cloud computing and Steve Jones comments on a few database related items.
IntelliSense in SQL Server 2008 can sometimes not be very intelligent. It’s there to help you can sometimes cause more...
By Brian Kelley
My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Comments posted to this topic are about the item Increase Deadlock Detection
Comments posted to this topic are about the item A Tool is Better than...
Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers