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?
Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
For most DBAs, normalization is an understood concept, a bread and butter bit of knowledge. However, it is not at all unusual to review a database design by a development group for an OLTP (OnLine Transaction Processing) environment and find that the schema chosen is anything but properly normalized. This article by Brian Kelley will give you the core knowledge to data model.
Continuing on looking at demo servers, this article presents an interesting solution to ensuring consistent demos that was deployed out in the field for a client company.
Microsoft tells us why it's so important to defend your code against malicious attacks.
The challenge for Robert Marda was to devise a way to keep the data available at all times while importing the new data, detect if a full or daily update was received and run appropriate data pumps, put in sufficient fail safes to ensure bad data would not get imported, and to make the process automatic including notification to pagers upon failure. Robert shows you how he did it here.
Are you using default values for your parameters? Using named parameters when you call the proc or passing the values by ordinal? Should you be? Andy thinks 6 out of 10 of our readers will agree with his point of view, we'll be a little more conservative and guess that 5 of out 10 will be closer.
Steve discusses a potential new project we have in the works. We'd appreciate as many comments and votes on this one as possible.
This article provides you with a simple stored procedure, that can search all the columns of all the tables in the current database, and replace a given search string with another string.
With SQL Server 2000 you are able to create databases or columns with a different collating setting than the server. This article will explain a couple of methods Greg has used to successfully change collation settings.
By Steve Jones
If someone is trying to convince you it’s not a pyramid scheme, it’s a...
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
In the era of cloud-native applications, Kubernetes has become the default standard platform for...
Hi experts, I have a 3+ TB database on a 2019 sql server which...
Comments posted to this topic are about the item The North Star for the...
Comments posted to this topic are about the item Multiple Escape Characters
In SQL Server 2025, I run this code (in a database with the appropriate collation):
SELECT UNISTR('%*3041%*308A%*304C%*3068 and good night', '%*') AS 'A Classic';
What is returned? See possible answers