This article explains how orphan users get created, and provides you with troubleshooting information. A bonus stored procedure called ShowOrphanUsers is included, that goes and searches all the databases and generates a complete list of orphan users.
In this article Andy looks at one way you can separate your presentation code from your data when you generate HTML tables for simple reports. Lots of code examples so you can see how it works.
This article shows you how to design the storage for email addresses, how to validate email addresses, how to retrieve demographic information from email addresses efficiently, using computed columns and indexes. It also covers the security aspect of dealing with email addresses.
A look at a new security tool from Microsoft for analyzing your SQL (and other) servers.
Certy.com has just released SQL Server 2000 certifications. These certifications are 100% free and a must for any DB developer & DBA.
The strength and holy grail of relational databases lies in the very name: relations. Microsoft has put a good deal of intelligence and cunning into query optimizations, caching, indexing and execution plans to make the process of finding related records even smoother and faster. This small article, however, will try to shatter the very sacred notion of relational databases.
Microsoft has released a patch to fix two buffer overflow vulnerabilities in SQL Server 2000. No UserID or password is required by the attacker to exploit these issues. The problem is exacerbated by the fact the attack goes over UDP.
The purpose of this article is to give you a working knowledge of how to view and understand query execution plans for SQL Server. This is part 1 in a series of articles that will walk you through understanding execution plans to help you improve your queries.
SQLClean is a SQL Tool that automatically creates a dependancy analysis of your SQL Server Database including tables, views, triggers, defaults, procedures etc. SQLClean will also analyze a client application for depenandies on SQL Objects allowing you to detect and eliminate unused SQL objects that are unreferenced by either the client app. or database itself.
From News.com, this series contains a bunch of interviews and surveys of a number of CTOs from large US corporations. Worth a read to see what the heavy spenders think.
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...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
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