Transactions in SQL Server are probably no more complicated than those in other RDBMS products, which is to say they are fairly complex. Don Peterson continues with part 3 of his series and takes a look at transaction isolation levels and how they interact with multiple connections and their impact on locking.
This is the twenty-fifth article of the series, MDX Essentials. The series is designed to provide hands-on application of the fundamentals of the Multidimensional Expressions (MDX) language, with each tutorial progressively adding features designed to meet specific real-world needs.
SQL Server 2000 is easy to administer relative to other RDBMS, but there is still plenty of room for improvement. Author Andre Vigneau has built a database toolkit to allow him to manage his cross platform databases. This is the second article in his series and deals with establishing connections to any database platform.
Have you ever wondered if you could start the execution of a stored procedure (SP) asynchronously from some T-SQL code? What I mean is starting the SP in the background and continuing on with the next line of code in your T-SQL script without waiting for the execution of the SP to complete. If so, then this article might be of some interest to you.
The default location for the SQL Server system databases doesn't always meet the standards of many organizations. Author Chris Hedgate has taken the time to put together a short checklist on how you can move the master, msdb, model, and tempdb databases easily.
The system table, "sysperfinfo," is the representation of the internal performance counters of SQL Server. This article demonstrates how to retrieve and store information from "sysperfinfo" to a CSV file, so that it can be analyzed.
SQL Server 2000 added XML support to allow some basiuc manipulation of XML data. At the time, XML was a hot buzzword in the computer industry and there were lots of applications being written to use XML. While the buzz has cooled, Jon Winer still uses XML in some interesting ways to make his life easier and his applications more rebust. Here he brings us a technique he's used to reduce the number of round trips required by an application.
Data Sanitization is the process of making sensitive information in non-production databases safe for wider visibility. This White Paper is an overview of various techniques which can be used to sanitize sensitive production data in test and development databases.
Creating an enterprise security plan is a complex endeavour. It involves evaluating multiple threats that gain access through many network paths to a hodgepodge of different applications and systems. With the focus on systems and paths, databases are frequently overlooked. Securing the database should be a fundamental tenet for any security practitioner when developing his or her security plan. The database is the source of data, the "crown jewels" in the information economy. Any security effort must start with this in mind and end with the strongest level of controls applied at the database layer.
SQLServerCentral.com wrapped up two weeks of voting by the community on the best third party products to help you with your SQL Servers. Read on to see who won.
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
By alevyinroc
I don’t recall where this came up (probably in SQLSlack), but I had a...
By Steve Jones
One of the parts of getting older that really sucks is I seem to...
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...
Comments posted to this topic are about the item Pushing the Limits of AGs
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers