When designing a database to support applications you need to consider how you are going to handle primary keys. This article explores natural and surrogate keys, and discusses the pros and cons of each, allowing you to determine what makes the best sense in your environment when you are designing your databases.
One Windows setting that I think is extremely important for SQL Server usage is the “Perform volume maintenance tasks” right,...
This week was T-SQL Tuesday week, the brainchild of Adam Machanic, and hosted by Pat Wright. The theme of Automation produced some very interesting posts. Some of them might inspire you to change the way you tackle the solutions for a variety of problems.
A review of SQL Monitor, the new DBA utility from Red Gate Software that can help you keep an eye on what your SQL Server instances are doing.
Today we have a reprint of an editorial from Sept 22, 2005. In this one, Steve Jones reminds you that blogging is a public event and you want to be careful about what you write.
I sometimes want to perform auditing or other actions in a trigger based on some criteria. More specifically, there are a few cases that may warrant an e-mail; for example, if a web sale takes place that requires custom or overnight shipping and handling. It is tempting to just add code to the trigger that sends an e-mail when these criteria are met. But this can be problematic for two reasons: (1) your users are waiting for that processing to occur, and (2) if you can't send the e-mail, how do you decide whether or not to roll back the transaction, and how do you bring the problem to the attention of the administrator?
Come learn about SQL Server in Phoenix on Feb 19, 2011. For free! Spread the word to anyone you know in the area.
Today we have a guest editorial from Andy Warren. Work can seem mundane and tedious at times, and today Andy asks you you remain engaged when the work isn't exciting.
Is there a way to not allow users to use SELECT * in their queries? New author AJ Raghuram has an interesting solution that can prevent this in code.
This article demonstrates using SQL Server's data mining capabilities with the Excel.
Next Monday, Marchg 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...
By HeyMo0sh
As someone who’s worked with data for over 20 years and with many cloud...
By HeyMo0sh
2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
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 REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers