Smit Dagli

Backend Software Engineer, with previous stints at Salesforce, Abnormal Security and a stealth startup

SQLServerCentral Article

A Few Best Practices for Strong SQL Server Security

Explore key strategies for securing SQL databases in this comprehensive guide. Learn about robust authentication, data encryption, SQL injection prevention, and more, with practical code examples. Enhance your database's security and performance by following tips from this article.

(2)

You rated this post out of 5. Change rating

2024-03-01

6,243 reads

Blogs

A Wellbeing Day at Redgate

By

It’s a day off for Redgate today. This is our annual wellbeing day, where...

Don’t Miss Out – SQL Server 2025 Unleashed Training Starts Next Monday!

By

Next Monday, March 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...

What is ALM in Fabric?

By

As someone who’s worked with data for over 20 years and with many cloud...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers