Viewing 15 posts - 52,951 through 52,965 (of 59,072 total)
It sounds like you're getting data from a file, cleaning it up, and then inserting it into a database... For 2.2 million rows, this shouldn't take more than a minute...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2008 at 12:02 pm
Heck yeah there would be performance issues... performance would increase because you could properly index it 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2008 at 11:08 am
simon.letts (1/9/2008)
To make it easier ...lets say that I just have a table with just one column, trans_code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2008 at 10:30 am
You would get a lot of help if you'd at least identify what it is what you want to do... 😉
But I understand... sometimes you're in a bit of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2008 at 9:44 am
k.furness (1/12/2008)
This is single table that contains the following Fields:
ID [int] Identity
QuestionnaireID [int]
Q0 [smallint]
.
.
.
Q150 [smallint]
Don't think I can get it any normalized than it is, but if I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2008 at 9:29 am
Actually... wasn't talking to him... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 10:11 pm
Heh... go around talking like those words, and you'll be labeled as pompous a$$ for sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:55 pm
If you have an answer to this, Ananth, just tell us... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:40 pm
If there's nothing that violates privacy laws or company policy, post the first ten lines of data so we can resolve this correctly, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:38 pm
This would be a good simple example for you to practice set based programming on... convert the cursor to set based.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:35 pm
The real fact is, you don't need BEGIN/END in a stored procedure. Try it... it's just allowed to make die hard Oracle programmers happy 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:22 pm
No... that's why the column number is "0". Read up on BCP Format Files... especially the example about skipping unwanted columns.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:19 pm
I'm with Steve... I use mixed case... it enforces capitalization and it's easier to hit the shift key than it is to hit the underscore when typing.
I agree with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:16 pm
Raghavender (1/11/2008)
Thank you for your reply
You didn't answer the question... What is it that you want to do and why do you think you need to modify the system tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:13 pm
As a DBA, you shouldn't... there's not much that can't be done in T-SQL with the possible exception of RegEx (Regular expressions) and, despite what Books Online says about the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2008 at 9:09 pm
Viewing 15 posts - 52,951 through 52,965 (of 59,072 total)