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
T-SQL Tuesday #198 Roundup: How Do You Detect Data Changes?
Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...
Optimizing Redshift Performance by Configuring WLM Queues
Efficient query performance in Amazon Redshift often comes down to how well you manage...
PowerShell Strikes Back: Return of the Loop
By gbargsley
Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...
Forums
Dealing with huge heap tables
Recently, our dev teams approach me for advice on improving their huge heap table...
Merge Replication failing with Error converting data type nvarchar to numeric
After upgrading 2 Merge Replicated databases to SQL 2022 and re-establishing the Merge Replication...
Why Your Index Isn't Being Used? - Reading Execution Plans to Find the Real Culprit
Comments posted to this topic are about the item Why Your Index Isn't Being...
Question of the Day
Distance Metric Algorithms
What are the distance metric algorithms that can be used in VECTOR_DISTANCE()?
See possible answers