Click here to Skip to main content
15,899,023 members
Home / Discussions / Database
   

Database

 
AnswerRe: INSERT Query Pin
Bernard Aoun1-Apr-07 5:57
Bernard Aoun1-Apr-07 5:57 
QuestionSelect Query Pin
Girish48131-Mar-07 18:57
Girish48131-Mar-07 18:57 
AnswerRe: Select Query Pin
jijoaresseriljose31-Mar-07 23:15
jijoaresseriljose31-Mar-07 23:15 
AnswerRe: Select Query Pin
Girish4811-Apr-07 3:34
Girish4811-Apr-07 3:34 
AnswerRe: Select Query Pin
Krish - KP6-Apr-07 4:42
Krish - KP6-Apr-07 4:42 
QuestionBest practice in large tables Pin
Nader Elshehabi31-Mar-07 10:10
Nader Elshehabi31-Mar-07 10:10 
AnswerRe: Best practice in large tables Pin
Colin Angus Mackay31-Mar-07 10:23
Colin Angus Mackay31-Mar-07 10:23 
GeneralRe: Best practice in large tables Pin
Nader Elshehabi31-Mar-07 10:36
Nader Elshehabi31-Mar-07 10:36 
Thank you Colin for your prompt reply I really appreciate it.

The table describes a medical procedure which contains 293 parameters to be filled in the report. Some of them of course can be null, but non of them is a repetition. Each procedure -ie. row- is given a GUID unique to that procedure used as the primary key.

My idea about dividing the table wasn't at the exact 50th column -maybe I wasn't clear on this point, sorry-. The procedure can be -somehow- roughly divided into several steps, each containing about 50 parameters. As you said this will give me a great headache in maintaining the relations between the tables using the procedure's GUID as a foreign key. Also in the quesries, this is going to be very troublesome.

Currently the table may work fine, but my concern is when it's filled with thousands of rows. Is it worth the effort to divide the table the way you suggested, or will it work fine as a single 293 columns containing table in the future?

RegardsRose | [Rose]

AnswerRe: Best practice in large tables Pin
kubben31-Mar-07 14:41
kubben31-Mar-07 14:41 
GeneralRe: Best practice in large tables Pin
Nader Elshehabi31-Mar-07 21:58
Nader Elshehabi31-Mar-07 21:58 
QuestionSQL Stored Procedure Column Pin
Lea Hayes31-Mar-07 9:24
Lea Hayes31-Mar-07 9:24 
AnswerRe: SQL Stored Procedure Column Pin
Colin Angus Mackay31-Mar-07 10:09
Colin Angus Mackay31-Mar-07 10:09 
GeneralRe: SQL Stored Procedure Column Pin
Lea Hayes31-Mar-07 10:17
Lea Hayes31-Mar-07 10:17 
GeneralRe: SQL Stored Procedure Column Pin
Colin Angus Mackay31-Mar-07 10:24
Colin Angus Mackay31-Mar-07 10:24 
Questionself join Pin
zizu9096@gmail.com31-Mar-07 5:31
zizu9096@gmail.com31-Mar-07 5:31 
AnswerRe: self join Pin
Colin Angus Mackay31-Mar-07 10:13
Colin Angus Mackay31-Mar-07 10:13 
AnswerRe: self join Pin
DQNOK2-Apr-07 6:55
professionalDQNOK2-Apr-07 6:55 
QuestionHow to calll Oracle stored procedures from Microsoft Reporting Services Pin
maskor ma31-Mar-07 1:36
maskor ma31-Mar-07 1:36 
QuestionError: DataBinding: 'System.Data.DataRowView' [modified] Pin
nothingbutcat30-Mar-07 16:25
nothingbutcat30-Mar-07 16:25 
QuestionComplex Select Query Pin
Girish48130-Mar-07 7:48
Girish48130-Mar-07 7:48 
AnswerRe: Complex Select Query Pin
DQNOK30-Mar-07 8:12
professionalDQNOK30-Mar-07 8:12 
GeneralRe: Complex Select Query Pin
Girish48130-Mar-07 8:28
Girish48130-Mar-07 8:28 
GeneralRe: Complex Select Query Pin
DQNOK30-Mar-07 8:39
professionalDQNOK30-Mar-07 8:39 
GeneralRe: Complex Select Query Pin
Jerry Hammond30-Mar-07 15:16
Jerry Hammond30-Mar-07 15:16 
GeneralRe: Complex Select Query Pin
DQNOK30-Mar-07 12:49
professionalDQNOK30-Mar-07 12:49 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.