Experimenting with Go-SQLCMD
Steve takes a look at go-sqlcmd, the newest evolution of the sqlcmd command line tool.
2023-04-21
7,913 reads
Articles
Extract SharePoint List Data and save to SharePoint Folder as CSV using Power Automate
Sometimes you might have your data within a SharePoint list, and you would prefer this dataset to be within a SharePoint folder instead for reasons like reporting in Power BI or Excel. You need to be able to move the data automatically from the SharePoint list to the SharePoint folder.
2023-04-21
SQL Prompt Safety Net Features for SSMS: Tab Coloring
The Tab Coloring component of SQL Prompt’s SSMS Tab management could save you from accidentally doing something apocalyptic on a production server, ever again.
2023-04-21
Firebase and Supabase: Key differences you need to know
Firebase is a NoSQL database, while Supabase is a relational database. The type of software you’re constructing determines which database is best for your project.
2023-04-19
PASS Data Community Summit registrations are open!
In 2023, connect, share & learn with like-minded peers, speakers, and industry leaders during the full week of data celebrations. Summit happens in person, from November 14th to 17th in Seattle. Check out the blog post to learn more.
2023-04-19
Create an Empty Database Using SQL Server Integration Services
Learn how to create a copy of an existing database without any data using Integration Services.
2023-04-17
3,652 reads
SQL Prompt Safety Net Features for SSMS: SQL History
Mistakes occasionally happen. Occasionally, you make some ill-judged 'refinements' to working code and now just wish you could rewind your tab back in time an hour and forget the whole sorry episode. Now and again, SSMS just conspires against you and crashes unexpectedly, and you lose all your currently open query tabs, some of which you hadn't saved. SQL History offers a useful safety net in the event of any of these unfortunate events.
2023-04-17
Use DDL Triggers to Automatically Keep SQL Server Views in Sync
As much as we tell people to use SCHEMABINDING and avoid SELECT *, there is still a wide range of reasons people do not. A well-documented problem with SELECT * in views, specifically, is that the system caches the metadata about the view from the time the view was created, not when the view is queried. If the underlying table later changes, the view doesn't reflect the updated schema without refreshing, altering, or recreating the view. Wouldn't it be great if you could stop worrying about that scenario and have the system automatically keep the metadata in sync?
2023-04-17
Data Oriented Cloud Security Mechanisms
This article looks at security mechanisms in the cloud that can help protect your data, with specific examples in AWS.
2023-04-14
1,406 reads
Three Use Case Examples for SQL Subqueries
There are many great tutorials on syntax, performance, and keywords for invoking subqueries. However, I wish to discover a tip highlighting selected SQL subquery use cases. Please briefly describe three SQL subquery use case examples. For each use case, cover how a subquery interacts with outer queries and the T-SQL for implementing the use case. Review excerpts from each example to show the value of implementing the use case.
2023-04-14
Blogs
RANK() vs DENSE_RANK(): #SQLNewBlogger
By Steve Jones
I haven’t done one of these in awhile, but I saw an article recently...
Using CAT for Testing of Data Agents
In last months one of the scenarios where you can use AI has been...
Are you getting value from your reporting?
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
Forums
Creating JSON II
Comments posted to this topic are about the item Creating JSON II
Engineer Lessons
Comments posted to this topic are about the item Engineer Lessons
Question of the Day
Creating JSON II
On SQL Server 2025, what happens when I run this code:
SELECT JSON_OBJECTAGG( N'City':N'Denver' RETURNING JSON) GOSee possible answers