2013-02-13
2,430 reads
2013-02-13
2,430 reads
2013-02-11
2,575 reads
2013-02-07
2,338 reads
2013-02-06
2,337 reads
2013-02-22 (first published: 2013-02-05)
1,825 reads
2013-02-05
2,284 reads
2013-02-04
2,315 reads
2013-02-01
2,328 reads
There are certain circumstances where SQL Server will silently truncate data, without providing an error or warning, before it is inserted into a table. In this tip we cover some examples of when this occurs.
2013-02-01
4,303 reads
2013-02-18 (first published: 2013-01-25)
2,807 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