Microsoft SQL Server 2000 Notification Services is the premier platform for developing and deploying a new class of scalable Web applications that deliver personalized, timely information updates to a variety of mobile devices. Review the resources on this page for details.
2002-09-18
3,314 reads
Do you get tired of reviewing each SQL Agent notifications nightly to determine which SQL Agent jobs failed? Is there a significant number of SQL Agent job notifications that it takes a while to review each? Here is an alternative that allows you to have a single email report of all job failures.
2002-09-17
11,736 reads
Having trouble with a target server (TSX)? Steve Jones did in his environment. Read about how he worked around the issue to restore administrative capabilities.
2002-09-16
7,239 reads
This program makes it easy to add and maintain extended properties for all objects in SQL Server 2000. Where as the Query Analyzer only allows you to maintain certain object SEPE allows all object to be maintained. This product is freeware for SQLServerCentral.com members.
2002-09-13
423 reads
SQL Server 2000 Enterprise Edition clocked an incredible 308,620 transactions per minute (tpmC)1 running on Windows .NET Server 2003, Datacenter Edition on an NEC TX7 server with 32 Intel Itanium 2 processors. The NEC system sets a new performance record on Windows, nearly doubling the best published 32-bit result. In addition, this Microsoft/Intel/NEC solution delivers the best price-performance of all results on the Top Ten performance list, at just $14.96/tpmC.
2002-09-12
3,369 reads
NGSSoftware have released NGSSQuirreL, a security audit and management tool for SQL Server. Designed to ease the administrative burden of securing SQL Server, NGSSQuirreL finds the security holes then generates a lockdown script based upon the vulnerabilities found so the server can be secured in a matter of minutes; and regular audits can help keep it that way. For more information or an evaluation copy please see the NGSSite - http://www.nextgenss.com/.
2002-09-11
464 reads
During the process of performance tuning queries and stored procedures there comes a time when you will notice that the execution plan selected by SQL Server is not the best plan. On occasion, everything you try doesnt cause SQL Server to choose the best way to execute your code. These are the times when hints can improve performance.
2002-09-10
9,451 reads
It's been a year since Steve Jones last wrote about the state of the DBA job market after the economy soured. Here's an update of the last year.
2002-09-09
4,497 reads
An interesting research paper by David Litchfield on how an attacker might go about attacking your server. Definitely worth a read.
2002-09-06
532 reads
Bitwise operators can be challenging to manage at first. However, with practice and patience, and under the right conditions, these operators can provide remarkable performance improvements in production environments. This article will compare two methods of accomplishing the same output, one with a normalized model and the other with bitwise operators.
2002-09-05
11,957 reads
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
By Steve Jones
Last week I asked you to write about SQL Server 2025 and what things...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
Comments posted to this topic are about the item SQL Server 2025 has arrived!
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers