2011-05-10
3,132 reads
2011-05-10
3,132 reads
The most persistent struggle in data processing has been to ensure clean data. There are many ways that data can be incorrect and a database must check, as best it can, that the data is correct. The CHECK constraint is ideally suited for this sort of work, and the checking routine can become quite complex when dealing with check digits in data.
2011-04-28
3,328 reads
This article examines the difference between adding a nullable column to a table or a column with a default value.
2011-04-27
5,393 reads
2011-04-26
3,162 reads
2011-04-25
3,076 reads
Remove tab,line feed and carriage return frome text field
2011-04-28 (first published: 2011-04-21)
3,370 reads
2011-04-18
2,825 reads
2011-04-13
3,214 reads
2011-04-08
3,268 reads
Retrieve the charindex of matching string for the desired occurrence
2011-04-13 (first published: 2011-04-06)
1,527 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