SCOME - Part 4: Using Visual Studio To Develop The Report
Part 4 of this series from Drew Salem shows how you build a report in Visual Studio.
2009-06-29
7,532 reads
Drew Salem
SCOME - Part 3: The Failed Jobs Report
Monitoring your servers centrally requires a good reporting system. Drew Salem continues with his SCOME journey to tame servers with the building of a job report in this article.
2009-04-24
7,533 reads
SCOME - Setting Up Your Remote Servers - Part 2
Continuing with his series on how to centrally monitor your SQL Servers, Drew Salem looks at how to set up remote servers.
2009-04-22
6,315 reads
SCOME - Centralize Monitoring with ASP.NET - Part 1
New author Drew Salem brings us a series on how to centrally monitor your SQL Servers. He includes ASP.NET code and a framework that will check your servers and display a report for you. This article presents an overview of the dealing with the SCOME issue.
2009-04-20
10,116 reads
Blogs
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
dataMinds Saturday 2026 – Slides
At Saturday the 21st of February I’m presenting an introduction to dimensional modelling at...
Forums
AllocationType as ROW_OVERFLOW_DATA
Hello, I inherited a number of tables with like 20-30 column using nvarchar(256) in...
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
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