CHECK constraints

External Article

Check your Digits

  • Article

The most persistent struggle in data processing has been to ensure clean data. There are many ways that data can be incorrect and a database must check, as best it can, that the data is correct. The CHECK constraint is ideally suited for this sort of work, and the checking routine can become quite complex when dealing with check digits in data.

2011-04-28

3,328 reads

Technical Article

RE: Cannot create a row of size 8171 which is greater than the allowable maximum of 8060

  • Reply

You probably didn't get much interest here, because this forum is for SQL Server 2005 (aka Yukon)!But it is true that the row size in SQL Server is limited to 8060 bytes.  There are at least two common ways to work around this problem.The first way is to change larger fields (if there are any) […]

You rated this post out of 5. Change rating

2004-09-16

Technical Article

RE: Creating a batch file to run multiple SELECT statements and output to a csv file.

  • Reply

Hello.If you still need a more detailed example then you may want to use the Build Query button in the Transform Data Task.  This option will give you a GUI that beahves somewhat like MS Access.If you need more detailed than that then you may want to state specifically which step is giving you trouble.

You rated this post out of 5. Change rating

2004-09-13

Technical Article

RE: RAISERROR failed due to invalid parameter substitution(s)

  • Reply

Somewhere in your code you are using the RAISERROR command and you are not supplying the correct parameters to the error string.  RAISERROR ('The level for job_id:%d should be between %d and %d.',       16, 1, @@JOB_ID, @@MIN_LVL, @@MAX_LVL)In the above example, the parameters @@JOB_ID, @@MIN_LVL, @@MAXLVL will be inserted into the error string 'The […]

You rated this post out of 5. Change rating

2004-07-07

Technical Article

RE: A senior moment?

  • Reply

The First /2.0 is a computed FORMULA for the median so it has to be DECIMAL or FLOATThe Second is just a count of RECORDS(ROWS)!! so it can't be a record and a half then you use /2HTH 

You rated this post out of 5. Change rating

2004-02-16

Technical Article

RE: Query Execution Time / Index

  • Reply

Because of the OR, you'll probably find a UNION faster, as it can seek (instead of scan) on each of the two indexed columns.  3 seconds for inserting 63,000 rows seems pretty fast to me, though.  With the query as written, you could certainly speed things up by using covering indexes, but then you write that […]

You rated this post out of 5. Change rating

2004-02-10

Blogs

Small Data SF 2024

By

I can’t remember how I heard about Small Data SF 2024, but it caught...

A New Word: Moledro

By

moledro – n. a feeling of resonant connection with an author or artist you’ll...

Snowflake + Azure blob

By

Let’s go back to data platforms today and I want to talk about a...

Read the latest Blogs

Forums

7 sept, scheduled book

By philip.scott

Comments posted to this topic are about the item 7 sept, scheduled book

7 sept, schedlued article

By philip.scott

Comments posted to this topic are about the item 7 sept, schedlued article

6 sept, published book

By philip.scott

Comments posted to this topic are about the item 6 sept, published book

Visit the forum

Question of the Day

Azure Data Lake Storage Gen 2

Azure Data Lake Storage Gen 2 is built on ...?

See possible answers