Treat All Sensitive Data as Important
No matter what the reason you have sensitive information, you need to treat it carefully.
2019-02-21
93 reads
No matter what the reason you have sensitive information, you need to treat it carefully.
2019-02-21
93 reads
2019-02-20
73 reads
Steve talks about the level of engineering effort we need in software development.
2019-02-19
90 reads
Steve talks about the need to be careful with backups in this age of malicious attackers.
2019-02-18
74 reads
2019-02-15
95 reads
2019-02-14
86 reads
Google was recently fined for GDPR violations. Steve wonders if their confusing documentation and tools are the problem.
2019-02-13
89 reads
Backblaze releases their new hard drive stats and there are some interesting items in the report.
2019-02-12
99 reads
It's not the zero'th time Phil Factor has complained about the madness of a binary collation.
2019-02-11
112 reads
A minor disaster for Steve reveals some cracks in his pre-DR planning.
2019-02-11
112 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
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...
Comments posted to this topic are about the item Adding Bits I
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