Removing Orphan Users from All Databases on Server
In this article by Greg Larsen, he shows you how to remove those pesky orphaned users that can be a security risk after restoring to a new server.
2002-11-18
16,139 reads
Articles
Best SoftTool Announces SQLSourceSafe 2.0
Best SoftTool, Inc. today announces that its flagship product SQLSourceSafe 2.0 is available for download and purchase. SQLSourceSafe is the integrated solution that Best SoftTool provides to meet the mounting market demand for a solid version control system for SQL Server database development. SQLSourceSafe integrates Microsoft Visual SourceSafe® and Microsoft SQL Server® together, offers robust and advanced version control functions to database scripts in SQL Server.
2002-11-18
59 reads
Creating Your Dream Project
In this article, columnist Christopher Duncan shows you how to create your dream development project.
2002-11-15
5,717 reads
What is the search order for Procedures prefixed sp_?
In this article, James Travis covers a common performance topic of prefixing stored procedures sp_. Does it really slow down performance?
2002-11-14
7,106 reads
A Sneak Peek at Entegra
Recently, the SQLServerCentral.com labs had the chance to get a sneak peak at Lumigents latest creation, Entegra, which is scheduled to ship in the second week in December. Entegra monitors database activity and provides a complete record of access to the data and changes to database structure and permissions.
2002-11-13
3,312 reads
Move Your Master
How often do you move your master database? Hopefully never, but this article looks at an easy technique should you need to perform this trick.
2002-11-12
10,034 reads
Worst Practice - Not Having An Archive Plan For Each Table
We're curious to see what our readers have to say about this one! How many of us have tables accruing data that won't be used and/or isn't of any value? At what point do we get rid of it to free up resources?
2002-11-11
9,249 reads
Streamlining the Database Server Recovery Process
Are you tired of manually restoring each database on a new server when the original server has a melt down? Does the manual process seem slow, and prone to keystoke and mouse click errors? Would you like to have those restore scripts automatically built, so you only have to fire them off? Well this article will show you one possible method for speeding up and reducing errors will trying to perform a restore of all databases on a server.
2002-11-05
9,038 reads
Why Secure the Database?
You're behind a firewall, you have passwords. Why spend any great amount of time on extra database security? Steve thinks there are a few reasons why in this article.
2002-11-04
4,492 reads
SQL Server Notification Services Documentation
Microsoft has released the "Books Online" equivalent for Notification Services. Browse through and take a look to see if this service is useful to you.
2002-11-01
694 reads
Blogs
Prime Day Recommendations
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
Fabric for Operational Reporting & SQL Endpoint Trap
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Crawl, Walk, Run with Agentic Development of Power BI Assets
If you’ve been watching AI roll through the data community and thinking, “this seems...
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...
Concurrency and Baseline Control: Level 5 of the Stairway to Reliable Database Deployments
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Spending Time in the Office
Comments posted to this topic are about the item Spending Time in the Office
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' ) GOSee possible answers