Writing Nearly Codeless Apps: Part 5
In this next installment of the series on writing codeless applications, David Ziffer looks at the querying of data from the database.
November Question: What steps do you include in your database maintenance?
Database maintenance is a critical task for every DBA. For this month’s question, list the typical steps that you use...
Showplan Operator of the Week – SORT
Fabiano introduces another ShowPlan operator that is used to build a query plan, or perform an operation specified in the DML. Once again, Fabiano demonstrates why it is important to be aware of these operators when getting queries to perform well.
SQLBIGeek’s Function Friday – Convert Job Duration to Seconds
Welcome to the second post of my “SQLBIGeek’s Function Friday” blog series. In this series, I am...
Life Without a Net
Today we have a guest editorial from Rodney Landrum that talks about life in the past, when we couldn't look up everything on the Internet.
Merge error handling
Learn to use recursion to determine which row caused your merge statement to fail in this article.
Creating Analysis Services Partitions Using BIDS
As your database grows in size, Analysis Services cubes that use that database grow along with it. As such, one...
Intelligent Conditional Split in an SSIS Package
Conditional Split is one of the most commonly used transforms in any SSIS Package development routine. The limitation with conditional split is that any record that satisfies the first condition from the conditions list is routed to its corresponding path exclusively. In a logical sense, a record might satisfy more than one condition and one might want the record to be routed to all paths for processing, but with the Conditional Split transform this is not possible. We need a more intelligent conditional split where we can selectively route the records to more than one output path. In this tip we will look at how to facilitate this intelligent conditional split.
A Faster BETWEEN Dates
This article shows us a different way of finding all records between 2 dates.
Can I really drop that index?
You believe that an index is unused and so could be removed, and yet, your finger hovers nervously over the metaphorical "delete" button. You can't quite bring yourself to do it. Is it really safe to drop this index? Tony wonders if "invisible indexes" might solve this dilemma.
Blogs
Five Ways Redshift Serverless Quietly Eats Your Budget
It is Friday, the queries are running, and nobody is watching the bill. That...
A Career of Memories
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Forums
Midjourney, Healthcare?
Comments posted to this topic are about the item Midjourney, Healthcare?
Changes, Happiness, and a Few Tears
Comments posted to this topic are about the item Changes, Happiness, and a Few...
BCP on Linux
Comments posted to this topic are about the item BCP on Linux
Question of the Day
BCP on Linux
When running bcp on Linux, what is the field terminator?
See possible answers