Additional Articles


External Article

Six Scary SQL Surprises

The working life of the DBA can be punctuated by surprises, but they aren't generally nice surprises. This is especially true if the DBA is not checking and monitoring the databases for obvious things such as database corruption, and disk space. However, the really scary surprises are less obvious and provide fewer warning signs. Brent Ozar gives six scary surprises that can be avoided by the shrewd DBA.

2017-10-31

7,099 reads

External Article

Backup SQL Server Databases in Parallel with PowerShell

I have a need to decrease the time my SQL Server database backups are taking to run. I thought about trying to run multiple backups at the same time to see if that would work. I could have created multiple SQL Server Agent Jobs to run at the same time, but I wanted a more dynamic way to handle this, so I created a PowerShell script that allows processes to run in parallel.

2017-10-30

3,911 reads

External Article

The SQL Server Features that Time Forgot

Every new release of SQL Server comes with new features that cause a ripple of excitement within the industry: well, amongst the marketing people anyway. What happens to all the exciting TLAs that are bandied about when a new version launches? It's mixed, it seems. Adam Machanic's classic post, The SQL Hall of Shame, has inspired Rob Sheldon to look back at some of the features that, though worthy, have may have failed to hit the mainstream.

2017-10-27

5,970 reads

External Article

SQL Server R Services: Working with ggplot2 Statistical Graphics

It is when you use R in SQL Server with one of the huge range of packages that comes with it that you can begin to appreciate the power of the system. With a package such as ggplot there are many 'knobs one can twiddle' in order to get spectacular and informative visualisations. Rob Sheldon continues his beginners series for R in SQL Server by showing how to refine the output to get it as you need it.

2017-10-25

3,267 reads

External Article

How to determine SQL Server database transaction log usage

One crucial aspect of all databases is the transaction log. The transaction log is used to write all transactions prior to committing the data to the data file. In some circumstances the transaction logs can get quite large and not knowing what is in the transaction log or how much space is being used can become a problem. So how to you determine how much of the transaction log is being used and what portions are being used?

2017-10-24

4,163 reads

External Article

Overview of Azure Data Lake

Azure Data Lake stores petabytes of data and analyzes trillions of objects in one place with no constraints. Data Lake Store can store any type of data including massive data like high-resolution video, medical data, and data from a wide variety of industries. Data Lake Store scales throughput to support any size of analytic workload with low latency. Read on to learn more.

2017-10-20

3,483 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Concurrency and Baseline Control: Level...

Spending Time in the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spending Time in the Office

Visit the forum

Question of the Day

Multiple Values Inserted

I have this code on SQL Server 2022. What happens when it runs all at once?

DROP TABLE IF EXISTS dbo.Commission
GO
CREATE TABLE dbo.Commission
(id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY
, salesperson VARCHAR(20)
, commission VARCHAR(20)
)
GO
INSERT dbo.Commission
( salesperson, commission)
VALUES
( 'Brian', 12 ),
( 'Brian', 'None' )
GO
 

See possible answers