2012-03-26 (first published: 2008-01-23)
3,294 reads
2012-03-26 (first published: 2008-01-23)
3,294 reads
2008-01-23
3,131 reads
2008-01-17
2,688 reads
2008-01-15
3,443 reads
The many popular rules concerning T-SQL filtering operators can't be trusted implicitly; instead, you should evaluate your options explicitly.
2008-01-14
2,792 reads
2011-09-20 (first published: 2008-01-11)
2,537 reads
Reformats the text output of queries to trim trailing blanks in wide varchar columns for easy copy-and-paste.
2008-03-10 (first published: 2008-01-09)
2,968 reads
2008-01-09
4,089 reads
Generate a "INSERT INTO...SELECT FROM" script for a table with an identity column.
2012-03-09 (first published: 2008-01-07)
4,271 reads
2008-01-07
3,917 reads
This is my late response to T-SQL Tuesday #204. I almost always forget about...
By Steve Jones
I was experimenting with CHOOSE() recently after I was asked a question. In a...
By DesertDBA
I did not expect 27 responses to my T-SQL Tuesday #204 invitation, but it...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
Comments posted to this topic are about the item Adding Bits II
Comments posted to this topic are about the item An Unlimited Token Budget
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] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, true)
GO
See possible answers