ne of the issues you face when building Web applications is handling the errors you encounter when interacting with a back-end database. I was recently working with someone to create a new Web site with SQL Server™, ActiveX® Data Objects (ADO), and ASP. Lots of little things came up that I thought were worth sharing with MIND readers, so I'll focus this column on what I learned from this experience and the solutions to many of the problems I faced.
P2P, the programmer's resource centre from Wrox Press, reached a milestone of 25,000 subscribers this week. To celebrate this fact, Wrox are giving away $1000 worth of books and ASPToday subscriptions in a free prize draw. For more details on how to enter, please visit: http://p2p.wrox.com/25k.asp. The draw will be made on July 16th.
This article by Neil Boyle looks at the enhancements to triggers that SQL Server 2000 brings.
This book discusses some of the issues that exist today in software. A good read for anyone developing software.
If you’re a programmer, you know that SQL is becoming more and more prevalent. Here’s a guide to one of its basic building blocks the stored procedure.
By Steve Jones
I don’t have SQL Server installed on my laptop. In an effort to keep...
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Hi all Can I get some perspective from the community please on performing in-place...
Comments posted to this topic are about the item How Long is a Long...
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers