David writes about the system he put together to handle addresses and the pros and cons of various techiques. Familiar with Soundex? He uses that too! Even though some of the info is specific to Great Britain, it's good reading. Addresses are one of the hardest pieces of information to handle!
2003-07-01
11,248 reads
This article, Part 2 – SQL Server 6.5 to 2000 Critical Upgrade Decisions and Redundant Upgrade Architecture, will begin to detail the technical components faced by the DBAs and Developers during the Upgrade process. The technical components detail the Critical Upgrade Decisions related to ANSI NULLS, Quoted Identifiers and other items.
2003-06-30
2,377 reads
As we mentioned before, Brian will be writing a column covering all facets of security. Turns out that there is so much to cover, he has agreed to write two columns per month! This article talks about the principle least privilege, why it doesn't always work, and some good info about removing the Builtin\Admin account.
2003-06-27
21,148 reads
Should your stored procedure continue when it hits an error? Or keep executing? What errors will cause a stored procedure to quit executing auotmatically? Regular columnist Robert Marda has at least some of the answers, we think you'll find this interesting.
2003-06-26
7,386 reads
This article from Veritas does a good overview of the complexities involved in managing a SAN. SAN's are here to stay, even if you don't have one, you should be reading about them.
2003-06-26
550 reads
Andy has been busy lately on a project you'll be hearing more about soon (!), but he did manage to get part four of his managing jobs series done. This article discusses ideas for patterns to follow when building jobs, including writing to the console, setting errorlevels, and how to get them installed on the server. DBA's, if you're not developers, look at this article - this is stuff you can take to your development team and get better/more manageable jobs.
2003-06-25
8,009 reads
New Author! Thom's first article discusses the difficulties you encounter when your database doesn't support cascading deletes (or you've opted not to use it) and you need to delete data in a child table based upon a value in the parent table. Not exactly your run of the mill delete query. Take a look and please rate/comment the article!
2003-06-24
5,284 reads
This article discusses various SQL Server Data Transformation Services (DTS) best practices. It is divided into sections like DTS naming conventions, DTS documentation, troubleshooting DTS packages, improving the performance of DTS packages, securing DTS packages, DTS resources.
2003-06-24
4,068 reads
Herve has done some work experimenting with max degree of parallelism (DOP) on some large multi processor blocks and based on that, has some recommendations for you if you're using more than 8 processors. Good reading!
2003-06-23
31,258 reads
David takes us through why he believes trying to run SQL and IIS on the same box is a bad idea. It's a common notion that it IS a bad thing to do, but you have real justification? Read this and you will!
2003-06-20
14,584 reads
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers