Technical Article

SQL Server 2005 Transactional Replication Agents

SQL Server 2005 replication agents are configured optimally out of the box, but occasionally you might need to alter the default behavior by tweaking the agent's parameters. SQL Server 2005 exposes some parameters through graphical interface that were available only from command line or through agent job steps in previous releases. Baya Pavliashvili encourages you to learn the new options available with each replication agent and how to fine-tune these options for your applications.

Technical Article

Monitoring File Sizes in SQL Server Part 1

Monitoring the file sizes and free space on your SQL Server can be done in a number of ways, but it needs to be done or you will get a phone call when you least expect it. In an interesting read, Roy Carlson brings us a great way with code and reporting to setup your own monitoring system.

Blogs

Word to the wise: don’t turn on SQL vulnerability checks on a blog about SQL

By

Recently, in an attempt to thwart leechers (1990s kids will know), I added some...

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...

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