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.
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.
This application will convert your schema into a standard Word document. Try before you buy, they have two versions - both under $200.
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.
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.
Continuing with our worst practices series, Steve Jones looks at another administrative no-no. Making a change to your live system on the fly.
David Gugick, SQL Server performance expert and software developer, provides over 100 tips on how to boost SQL Server performance.
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.
By Zikato
I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...
Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...
By Steve Jones
We aren’t the only company that does this, but Redgate Software does try to...
Comments posted to this topic are about the item A Challenge of Our Knowledge
Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...
Comments posted to this topic are about the item Transaction Log Truncation
In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?
See possible answers