2017-10-06
1,115 reads
2017-10-06
1,115 reads
There are several obvious problems with poor SQL Coding habits. It can make code difficult to maintain, or can confuse your team colleagues. It can make refactoring a chore or make testing difficult. The most serious problem is poor performance. You can write SQL that looks beautiful but performs sluggishly, or interferes with other threads. A busy database developer adopts good habits so as to avoid staring at execution plans. Rob Sheldon gives some examples.
2017-10-05
6,056 reads
2017-09-29
1,047 reads
2017-09-26
1,196 reads
A note of caution on the use of sp_helptext to script out objects.
2017-09-25
2,878 reads
2017-09-22
1,141 reads
2017-09-21
937 reads
2017-09-18
1,178 reads
2017-09-12
1,038 reads
When we have to deal with and store a lot of data, it makes sense to aggregate it so that we store only the information we actually need. If we get this right, this works well, but the design of the system takes care and thought because the problems can be subtle and various. Joe Celko describes some of the ways that things can go wrong and end up providing incorrect, inaccurate or misleading results.
2017-09-12
3,866 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