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,767 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

Presenting with Visual Studio Code

By

A while back I wrote a quick post on setting up key mappings in...

Advice I Like: In 100 Years

By

In 100 years a lot of what we take to be true now will...

RANK() vs DENSE_RANK(): #SQLNewBlogger

By

I haven’t done one of these in awhile, but I saw an article recently...

Read the latest Blogs

Forums

connections vs apis

By stan

hi , i hear more and more that we have too many connections to...

is it true we cant debug c# scripts in ssis anymore under vs

By stan

Hi, i'm running vs2022.   I'm trying out a c# script that i'd like to...

Missing the Jaro Winkler Distance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Missing the Jaro Winkler Distance

Visit the forum

Question of the Day

Missing the Jaro Winkler Distance

I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:

SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:
Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.
What is wrong?

See possible answers