Articles

Technical Article

Utilize SQL Server Storage Effectively

With the increased use of databases and the need to have more and more data online, database storage is an area DBAs need to manage effectively. If you plan your database and data management correctly you can build and manage a cost effective, high performing SQL Server solution. If not, you risk potential storage issues as well as performance degradation. This session will cover best practices and options focused on helping you manage your SQL Server storage. We will dive into the tools you can use to manage database storage, some of the latest trends, database design implications, data archiving and alternatives such as compression, BLOB data storage, filtered indexes and more. We’ll also introduce a tool that allows you to reduce the storage footprint of your live SQL Server databases.

Join us for this free event and learn how to utilize your SQL Server storage effectively.

(1)

You rated this post out of 5. Change rating

2012-08-14 (first published: )

5,555 reads

External Article

Using DELETE CASCADE Option for Foreign Keys

Referential integrity is a very important thing to consider when designing a database. In my years as a DBA I've seen database designs that sit on both ends of the spectrum, none at all and cases where every table is linked to multiple tables. While the later certainly can be a little more difficult to work with it ensures the integrity of your data stays intact. The other end provides much more flexibility when it comes to updating and deleting data from your database, whether it's being done through the application or directly on the backend, but has the issue of possible orphan records if things are not done properly. This tip will look at the DELETE CASCADE option when creating foreign key constraints and how it helps keep the referential integrity of your database intact.

2012-08-13

3,973 reads

SQLServerCentral Article

SQL Server 2012’s Information on Parallel Thread Usage

In the SQL Server 2012 execution plan we can see better the true thread reservations for a query and not just information on the maximum degree of parallelism and row distribution across parallel threads; thanks to the new parallel thread usage information.

(17)

You rated this post out of 5. Change rating

2012-08-09

5,768 reads

External Article

Removing the SQL Server Management Data Warehouse

SQL Server 2008 introduced a new feature, Management Data Warehouse (MDW), which allows users to collect metrics on their servers over time to aid in performance troubleshooting. A lot of people try this feature out, because it is easy to set up, and then find that it is not so easy to remove. In fact, removing MDW is not supported; in SQL Server 2012, though, a new system stored procedure was added to make this process easier. The problem is that this stored procedure (as well as several of the workarounds I've seen published) can leave several objects behind.

2012-08-09

2,418 reads

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Tmn. Harapan Indah. Tlp:085373737845

By clevercracks444

BCA KCP Tmn. Harapan Indah. Tlp:085373737845.Komp. Taman Harapan Indah Blok EE No.1, Jelambar Baru,...

BCA KCP Pluit Kencana Tlp (+62 821°3111°179

By Top Xe

Jl. Taman Pluit Kencana Selatan No.1-3, RT.4/RW.6, Pluit, Kecamatan Penjaringan, Jkt Utara, Daerah Khusus...

Wisma BCA BSD Tlpn/wa:085373737551

By balijepalli.p

Jl. Pahlawan Seribu No.8, Lengkong Gudang, Kec. Serpong, Kota Tangerang Selatan, Banten 15310

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers