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,084 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,094 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,773 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,920 reads
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.
2003-01-14
7,059 reads
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.
2003-01-13
18,702 reads
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.
2003-01-13
3,634 reads
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
By Steve Jones
Last week I asked you to write about SQL Server 2025 and what things...
Hi everyone, I’m working with some old SSIS 2005 packages, and I’m trying to...
Unlock the full potential of spreadsheets with our “Advanced Excel Mastery” course tailored for...
Prepare your team for the upcoming compliance shift with our “2025 Form 1099 Reporting...
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers