Kill–use this weapon carefully in SQL SERVER . TIP #90
When we heard “Kill” then first impression of this word is very bad. We always scare with this word.
In...
2015-03-03
677 reads
When we heard “Kill” then first impression of this word is very bad. We always scare with this word.
In...
2015-03-03
677 reads
2015-03-03
5 reads
2015-03-03
7 reads
2015-03-03
7 reads
2015-03-03
15 reads
In this session Prakash will walk through the process implemented to alleviates many of the pain points for deploying, managing,...
2015-03-03
556 reads
I am pleased to be presenting a highly interactive session tomorrow evening that is a full end-to-end setup and management...
2015-03-03
433 reads
In part 3 of this series of blogs on "getting more agile" I am going to look at unit testing...
2015-03-03
412 reads
In part 3 of this series of blogs on “getting more agile” I am going to look at unit testing and why we need to do it.
My code is...
2015-03-03
21 reads
In part 3 of this series of blogs on “getting more agile” I am going to look at unit testing...
2015-03-03
68 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...
Comments posted to this topic are about the item Helping an English Student with...
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