Avoiding Logging
It seems that some people think that you can perform actions in SQL Server without logging them in the transaction log. Steve Jones talks about this myth and says it's not even an option he'd like to have.
It seems that some people think that you can perform actions in SQL Server without logging them in the transaction log. Steve Jones talks about this myth and says it's not even an option he'd like to have.
Join this webinar from Pluralsight, a very well known developer training company. Learn how SQL Source Control can help you keep track of your code.
SQL Server is able to make implicit use of parallelism to speed SQL queries. Quite how it does it, and how you can be sure that it is doing so, isn't entirely obvious to most of us. Paul White begins a series that makes it all seem simple, starting at the gentle level of counting Jelly Beans.
Phil Fator, the self-confessed wild man of T-SQL, finally comes clean: he's a secret PowerShell user. But for the DBA, what is PowerShell without SMO? Is Microsoft giving the latter the care and attention it needs?
Steve Jones talks about the way business ought to run, with more long term goals and objectives taking precedence over short term revenue. One idea that might help us is having a wisdom department that looks forward and tries to grow the business for the long term.
This challenge invites you to write a query that converts binary values into decimal format.
When I read various forums about SQL Server, I frequently see questions from deeply mystified posters. They have identified a slow query or stored procedure in their application. They cull the SQL batch from the application and run it in SQL Server Management Studio (SSMS) to analyse it, only to find that the response is instantaneous. At this point they are inclined to think that SQL Server is all about magic. A similar mystery is when a developer has extracted a query in his stored procedure to run it stand-alone only to find that it runs much faster – or much slower – than inside the procedure.
The second part of Steve Jones' series on coding standards within SQL Server.
Often in database design we store different values in rows to take advantage of a normalized design. However many times we need to combine multiple rows of data into one row for a report of some sort. New author Carl P. Anderson brings us some interesting T-SQL code to accomplish this.
This Friday Steve Jones talks about the commitments and contracts that you may have with your customers. Do you know what they are? Is the contract explicitly spelled out? Take this Friday's poll and share your answer with everyone else.
By Steve Jones
I wrote about learning today for the editorial: I Can’t Make You Learn. I...
By ReviewMyDB
Fabric has CI/CD built in, but if you've tried to use it for database...
By Steve Jones
attriage – n. the state of having lost all control over how you feel...
Comments posted to this topic are about the item Forward Deployed Engineers
Comments posted to this topic are about the item TRY_PARSE vs TRY_CONVERT in SQL...
Comments posted to this topic are about the item DBCC CHECKDB Limits II
I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?
See possible answers