loading and reformatting text file data into into SQL table

Question

loading and reformatting text file data into into SQL table

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Jeff Moden (5/30/2015)
1. Do you want to capture the fact that the items after the @ symbol change?
2. In the case of things like "hicks2001" "conference:06", what do you want done with THAT data?
3. What do you want done with the braces and double quotes around the items?
Maybe it would be easier to just ask you what the data from above should look like in a table?

Not the OP, but I am very familiar with BibTex, so for future reference

1) Yes, absolutely. The required and optional attributes differ based on the various categories. @Book will have title and publisher, @article will have both a paper title and a journal. @InProceedings will have a title and booktitle and optionally page numbers.

2) Those are the lables for the entries. They'll need to be in the table, they're unique. The way that Bibtex and LaTeX work is that in the document there'll be an \cite{hicks2001} and when the document is compiled the \cite reference is replaced by something like "(von Hicks, M, 2001)", depending on the styles used.

3) The brackets and " are like { in JSON or <> in XML, just wrappers.

I would not accept that file format.
Specify the file format and make life easier on yourself.

If you work in academia or are writing papers, BibTex is one of the main formats for references and citations.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 2

GilaMonster (5/31/2015)
Jeff Moden (5/30/2015)
1. Do you want to capture the fact that the items after the @ symbol change?
2. In the case of things like "hicks2001" "conference:06", what do you want done with THAT data?
3. What do you want done with the braces and double quotes around the items?
Maybe it would be easier to just ask you what the data from above should look like in a table?
Not the OP, but I am very familiar with BibTex, so for future reference
1) Yes, absolutely. The required and optional attributes differ based on the various categories. @Book will have title and publisher, @article will have both a paper title and a journal. @InProceedings will have a title and booktitle and optionally page numbers.
2) Those are the lables for the entries. They'll need to be in the table, they're unique. The way that Bibtex and LaTeX work is that in the document there'll be an \cite{hicks2001} and when the document is compiled the \cite reference is replaced by something like "(von Hicks, M, 2001)", depending on the styles used.
3) The brackets and " are like { in JSON or <> in XML, just wrappers.
I would not accept that file format.
Specify the file format and make life easier on yourself.
If you work in academia or are writing papers, BibTex is one of the main formats for references and citations.

Thanks, Gail. Very interesting. The Wikipedia link that was provided earlier is pretty interesting, as well.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 3

Thank you. I appreciate your feedback. Excuse me.

I was just trying to make it easier this is a very interesting subject.:-)

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/