Every DBA needs a few tricks up his/her sleeves to help them better manage their SQL Server 2000 environment. In this article I will explore a couple of such tricks. I will first explore how to cycle the SQL Server error log, and why you might want to do this. Secondly I will discuss backup history information and why you would need to periodically remove some of the older history information.
Are you thinking about consolidating your SQL Servers on to fewer machines? It is an interesting idea and one that is definitely more possible with SQL Server 2005 and 64-bit servers. Steve Jones takes a look at some of the pros and cons of moving to fewer servers.
Excerpted from Brian Larson's book Microsoft SQL Server 2005 Reporting Services 2005, this chapter will help you build a table report and matrix report without the use of the Report Wizard, and it will discuss two new report types -- the chart report and the list report.
One of the big complaints in SQL Server development has been error handling. SQL Server 2005, however, substantially enhances its capabilies in this area and Leo Peysakhovich brings some code that provides a template for adding error handling to your application.
One advantage of CLR assemblies is the ability to consume web services from within the database. This wouldn’t be easy with T-SQL, and would also require a lot of work in an unmanaged extended stored procedure. With .NET, it’s almost as simple as accessing a local DLL. There are just a couple of extra command-line utilities we need to run to be able to access web services from within a SQL assembly:
SQL Server 2000 has a rock solid backup scheme , but do you really need to run full backups every day? What if you could decide on the fly if it was more efficient for a full or a differential backup? Darwin Hatheway brings us the basis for a scheme that can predict the size of a differential backup by examining how much of the database has changed.
Server 2005 now supports a more programmable error trapping convention in T-SQL code. This error handling is known as the TRY/CATCH block. The TRY/CATCH block allows T-SQL to handling errors like other programming languages, such as Microsoft Visual C# and C++. In addition to the TRY/CATCH block, Microsoft has expanded the set of available system functions in SQL Server 2005 for returning error codes and messages when an error occurs in your T-SQL code. This article will explore the new TRY/CATCH block and explain the new system functions for returning error codes and messages.
Rules play a central role in a wide variety of applications. In addition to the declarative specification of business rules, the simple rule engine design described in this article can be used to implement state machines, predicate dispatchers, or any other rule-based system.
Do you have a need to generate bar codes for an application? Check out this new product, reviewed by Dinesh Asanka, that uses Reporting Services to help you easily print bar codes.
In the past, it was common for an employer to work with their employees and pay to keep their skills current. While this still happens, in this age of high employee (and employer) turnover, many companies are more circumspect about how much they will spend to keep their employees keep up-to-date. At the end of the day, it is your responsibility to make sure this happens and there are many good reasons why you should strive to do so and many ways in which you can do it.
By Steve Jones
I was listening to the radio the other day and the hosts were discussing...
By Steve Jones
We’re a week late, once again my fault. I was still coming out of...
By Steve Jones
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
Comments posted to this topic are about the item Learning From Breakage
Comments posted to this topic are about the item Python in Action to Auto-Generate...
Comments posted to this topic are about the item Adding and Dropping Columns I
I have this table in my SQL Server 2022 database:
CREATE TABLE [dbo].[CityList] ( [CityNameID] [int] NOT NULL IDENTITY(1, 1), [CityName] [varchar] (30) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ) ON [PRIMARY] GOI decide to add two new columns for the StateProvince and Country. What code should I use? See possible answers