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
Advice I Like: Respect
By Steve Jones
“Don’t aim to have others like you; aim to have them respect you.” –...
Setting Up a Mac for Data Engineering and AI Work
If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...
Want to look at cloud reporting but not sure what the costs will be?
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
ALAMAT KANTOR BCA KCP Santa Tlp,Cs:0821-8154-393
WA:08218154393 Jl. Wolter Monginsidi No.54, RT.2/RW.4, Petogogan, Kec. Kby. Baru, Kota Jakarta Selatan, Daerah...
ALAMAT KANTOR BCA KCU THAMRIN Tlp,Cs:0821-8154-393
WA:08218154393 Menara BCA, Grand Indonesia, Jl. M.H. Thamrin No.1, RT.1/RW.5, Menteng, Kec. Menteng, Kota...
Question of the Day
BIT_COUNT I
In SQL Server 2025, I have a table (dbo.UserPermission) that contains this data:
UserID UserPermissions 15 23 37What is returned when I run this code:
select bit_count(UserPermissions) as PermissionCount from dbo.UserPermission where UserID = 3;See possible answers