2009-06-01
4,544 reads
2009-06-01
4,544 reads
2009-05-27
5,421 reads
2009-05-25
3,316 reads
2009-05-25
1,645 reads
2009-05-21
4,598 reads
2009-05-20
4,589 reads
2009-05-19
3,697 reads
This article is for newbies who have just started their career in SQL development. Everyone might have faced this problem when importing or inserting data into tables when they accidentally put the data in the wrong columns. The first thought would be to delete the data and start over, but in this tip we look at a simple solution to swap the data.
2009-05-13
2,356 reads
The ROW_NUMBER function has drastically changed the way we can write a number of queries in T-SQL. New author Francis Rodrigues brings us a few places where this function can improve the efficiency of your code.
2010-01-29 (first published: 2009-05-12)
72,927 reads
2009-05-11
4,543 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