This series of articles will examine the purposes, uses, and optimization of cursors in SQL 2000. SQL languages are designed so groups of records, or sets, can be manipulated easily and quickly. The speed at which groups of data can be altered, updated and deleted, demonstrates why working with sets is the preferred method. However, there are places where cursors are a better choice.
The next version of SQL Server due in 2005 will bring about many changes in how it works, with .NET, the CLR integration, Integration Services, and much more. Many of us are looking to get a jump on the product and see where these changes might affect our scripts and environments. Jon Reade has started the work in decoding the new DBCC commands, which ones work and which don't. Since there's a limited amount of documentation for the Beta product, read about his detective work and send him off an
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.
In last months one of the scenarios where you can use AI has been...
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
I have two challenges XML source control not displaying the XML file parent node...
Thanks in advance for any clues on this. I am trying to write a...
Comments posted to this topic are about the item Backup to Immutable Storage
In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?
See possible answers