Additional Articles


Technical Article

SQL Server Management Features vs Oracle Database Management Features

The usefulness and utility of the SQL Server Agent cannot be overstated. Oracle Database supports the automatic starting of an instance, so whatever is associated with the Oracle instance can also be started along with the instance. The same holds true with the SQL Server instance and its agent service.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2010-05-06

3,650 reads

External Article

SQL Server 2008 System Functions to Monitor the Instance, Database, Files, etc.

SQL Server provides several system meta data functions which allow users to obtain property values of different SQL Server objects and securables. Although you can also use the SQL Server catalog views or Dynamic Management Views to obtain much of this information, in some circumstances the system meta data functions simplify the process. In this tip I am going to demonstrate some of the available system meta data functions and their usage in different scenarios.

2010-05-05

3,353 reads

Technical Article

A Perspective on Database Performance Tuning

Fundamentally, database performance tuning is done for two basic reasons, to reduce response time and to reduce resource usage, both of which can apply for any given situation. Julian Stuhler looks at database performance tuning, and why it remains one of the most important topics for any DBA, developer or systems administrator.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(3)

You rated this post out of 5. Change rating

2010-04-30

5,074 reads

External Article

Consolidating SQL Server Error Logs from Multiple Instances Using SSIS

SQL Server hides a lot of very useful information in its error log files. Unfortunately, the process of hunting through all these logs, file-by-file, server-by-server, can cause a problem. Rodney Landrum offers a solution which will allow you to pull error log records from multiple servers into a central database, for analysis and reporting with T-SQL.

2010-04-28

2,955 reads

Technical Article

How to Evict a Failed Node and Add it Back to SQL Server 2005 Cluster

Adding and removing nodes in SQL Server Clusters is not so difficult, and instructions on how to do so abound on the internet. However, mismanagement when adding/removing nodes can quickly become a 'gotcha' that wastes time. Bo Chen offers insight into some of those scenarios that are not normally covered in the standard online documents.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2010-04-26

2,048 reads

Blogs

Dazzling Stuff in Databricks (SQL) – Qualify

By

Once upon a time I had a series about some cool stuff in Snowflake:...

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

A CLR Assembly Broke My Availability Group

By

Sounds scary! Did I get your attention?

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers