2009-04-28
3,752 reads
2009-04-28
3,752 reads
This article discusses a common mistake while making date comparisons in T-SQL and its resolution. From new author Manish Sinha.
2009-04-28
16,176 reads
Learn to use Where, Claire. Plus a conversion methodology, a test harness and more!
2010-07-02 (first published: 2009-04-27)
28,549 reads
2009-04-23
4,583 reads
2009-04-22
4,373 reads
2009-04-21
4,569 reads
2009-04-17
3,764 reads
2009-04-14
4,413 reads
Learn how to leave those Cursors and loops in the thrash, Nash... An article from longtime contributor and SQL expert, Barry Young.
2010-06-25 (first published: 2009-04-14)
34,252 reads
2009-04-13
4,728 reads
Once upon a time I had a series about some cool stuff in Snowflake:...
By Steve Jones
“Most overnight successes – in fact any significant successes – take at least 5...
Telp/Wa 62817825533 Jl. Cempaka No.17, Sukorejo, Kec. Sukorejo, Kota Blitar, Jawa Timur 66111
Telp/Wa 628217555651 Jl. Gajah Mada No.14-18, Kelurahan Jember Kidu, Jember Kidul, Kec. Kaliwates, Kabupaten...
Comments posted to this topic are about the item Why Successful SQL Server Backups...
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