SQLServerCentral.com is all about learning. Our goal has been to build a community where we all teach each other how to become more proficient with SQL Server. Most of our content to date has been written articles that show you how to do something. Well we have a a better idea, maybe. Check out our new video HOWTO series.
A common complaint of database administrators (DBAs) is that performance bottlenecks are not among those problems that one can fix "by just throwing hardware at it." Thus, database servers must provide tools and techniques to help administrators address this issue. On that aspect, SQL Server 2005 does not disappoint.
SQL Server has this concept of an owner of an object. Similar to the concept of schema, but not quite the same. Best practice dictates that all objects in SQL Server be owned by dbo, but that does not always happen. Tracking those objects down might be a pain, but Santveer Singh brings us an easy way of doing this.
Learn how to achieve scalable, high-performance merge replication applications. (White Paper)
Destroyed your database? Corrupted files? What about corrupted records? What do you do in SQL Server? MSSQLRecovery is a product that can help you with this and more. Read this review by Dale Elizabeth Corey and see if this product might be something you can use.
One of the age old problems in DTS is moving packages between your development, test and production environments. Typically a series of manual edits needs to be done to all the packages to make sure that all the connection objects are pointing to the correct physical servers. This is time consuming and gives rise to the possibility of human error, particularly if the solution incorporates many DTS packages. Many companies have provided their own custom solutions for managing this problem but these are still workarounds for a problem that is inherently DTS's.
Deploying a SQL Server database with your software can be tricky. It's easy to forget something that you added to development when trying to script out or detach and copy a database. And there's the whole problem of integrating the installation or upgrade into your main installation routine. New author Mark Vermeulen takes a look at Red Gate's SQLPackager, designed to make the job of deploying a database much easier.
The key to effective security is embracing it as an ongoing process rather than a one time event. This document examines how database security can be enhanced with a proactive security lifecycle approach.
A look at coding standards in SQL Server. The first part of this series deals with object naming standards.
A short survey from Microsoft looking for feedback from users in order to try and improve the application development process. If you build applications with MS technolgies, especially SQL Server, take a moment and respond.
By Steve Jones
I got a notification from a question I’d posted at SQL Server Central: Getting...
By SQLPals
SQL Server sa Account Security: Rename, Disable & Best Practices In...
By Brian Kelley
Artificial Intelligence and quantum computing are two areas of emerging technology that receive most...
Comments posted to this topic are about the item Are You Working More Hours?
Comments posted to this topic are about the item Stairway to Reliable Database Deployments...
Comments posted to this topic are about the item A Limited Startup
I add this parameter to SQL Server 2025 in the Configuration Manager:
-mDynamicsWhat does this do? See possible answers