Risky Behavior
An interesting debate from one of my editorials on risk. Some great points raised by everyone, but I still think...
2007-08-07
609 reads
An interesting debate from one of my editorials on risk. Some great points raised by everyone, but I still think...
2007-08-07
609 reads
2007-08-07
1,693 reads
2007-08-06
1,707 reads
Part 3 of Steve Jones' series on beginning SQL Server from the perspective of a system administrator or someone not used to working with SQL Server. If you've been designated the new administrator, take a look at this series for some help in coming up to speed on this product. This article looks at logins and basic security.
2007-08-03 (first published: 2004-09-02)
41,661 reads
We've dropped an acronym!
In my rounds of the blogs today, a number of people have pointed out that SQL Server...
2007-08-03
549 reads
2007-08-03
1,697 reads
2007-08-02
1,712 reads
I'm downloading now, and you need some sort of inviation to do so, but it's available and ready for you...
2007-08-01
621 reads
2007-08-01
1,674 reads
2007-07-31
1,747 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
WhatsApp:0817819444 Jl. Mahendradatta Selatan No. 99 AX, Padangsambian, Kec. Denpasar Bar., Kota Denpasar, Bali...
WhatsApp:0817819444 Jl. Raya Sesetan No.301, Sesetan, Denpasar Selatan, Kota Denpasar, Bali 80223
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