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
SQL, MDX, DAX – the languages of data
By DataOnWheels
Ramblings of a retired data architect Let me start by saying that I have...
Setting PK Names in Redgate Data Modeler
By Steve Jones
A customer was testing Redgate Data Modeler and complained that it auto-generated PK names....
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
Forums
Connecting Power BI to SSAS and effective user not working
Hi everyone, Below is a consolidated summary of what we validated Architecture & data...
High Availability setup - has anyone seen this method?
Hi all, I recently moved to a new employer who have their HA setup...
Semantic Search in SQL Server 2025
Comments posted to this topic are about the item Semantic Search in SQL Server...
Question of the Day
Encoding URLs
I have this data in a SQL Server 2025 table:
CREATE TABLE Response ( ResponseID INT NOT NULL CONSTRAINT ResponsePK PRIMARY KEY , ResponseVal VARBINARY(5000) ) GOIf I want to get a value from this table that I can add to a URL in a browser, which of these code items produces a result I can use? See possible answers