Block the DBA?
Can you block a DBA from performing certain actions on a server if he has sysadmin rights? The real answer is no, but this article shows you how to block an unknowledgable DBA from performing certain actions.
2003-01-28
6,877 reads
Can you block a DBA from performing certain actions on a server if he has sysadmin rights? The real answer is no, but this article shows you how to block an unknowledgable DBA from performing certain actions.
2003-01-28
6,877 reads
On Friday the 24th, a virus that preys on a SQL Server vulnerability began to attack networks, taking down many networks. This brief network describes the virus and how to protect yourself from it.
2003-01-27
10,815 reads
Moving SQL Server from one computer to another is not a very difficult thing to do, but it often stumps newbie DBAs. Of course, it needs careful planning to ensure that the SQL Server is moved completely and properly to the new machine, and with a minimal downtime and no data loss. This article introduces you to a couple of methods you can employ to move/migrate SQL Server from one computer to another.
2003-01-24
107 reads
This one is pretty interesting, Andy discusses a few things he sees in comments that not only fail to add value, they end up costing extra time. There's room for discussion here, but definitely a discussion worth having - comments can make you or break you, here's a chance to think about what you think is important in commenting and pass that on to your development team.
2003-01-23
11,112 reads
This application will convert your schema into a standard Word document. Try before you buy, they have two versions - both under $200.
2003-01-23
623 reads
Because of the way date and time values are stored in SQL Server, searching for a particular date or time is not as straightforward as you might think it would be. This article describes how date/time values are stored, how the database design can simplify (or complicate) data retrieval, and how to query date/time data to get the right results every time.
2003-01-21
36,125 reads
This article is the first of a series that I plan on writing and placing on my website to help other DBAs in auditing a new SQL Server environment. This article deals with determing which SQL Server logins have weak passwords, with the definition of weak being, no password, password the same as the login name or having a password of only one character.The stored procedure used for this article is embedded in the article and it has been submitted as a independent script named spAuditPasswords.
2003-01-21
66 reads
Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.
2003-01-20
7,777 reads
David Gugick, SQL Server performance expert and software developer, provides over 100 tips on how to boost SQL Server performance.
2003-01-17
88 reads
You have spent thousands of dollars on that cool technology; clustering, redundant controllers, redundant disks, redundant power supplies, redundant NIC cards, multiple network drops, fancy tape backup devices and the latest and greatest tape technology. You are all set. There is no way your going to have downtime. Right?
2003-01-16
4,925 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers