StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18751023
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-11T20:50:04.687
FavoriteCount
0
LastActivityDate
2013-09-11T20:50:04.687
LastEditDate
LastEditorUserId
0
OwnerUserId
61305
ParentId
18750372
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
There are a couple of problems here: <ol> <li>I suspect there isn't a valid <code>\n</code> on the first line. Otherwise SQL Server wouldn't munge the first two rows when you change to <code>FIRSTROW = 1</code>.</li> <li>Using <code>","</code> as the column delimiter works great for all of the columns except the first and the last column. This leaves a leading <code>"</code> on the first column, and a trailing <code>"</code> on the last column. You can deal with the latter by changing your <code>ROWTERMINATOR</code> to <code>"\n</code>, but that will only work if you can also add a trailing <code>"</code> to the header row (during the process of ensuring that there is a valid <code>\n</code> there). At that point you may as well make sure that the header row matches the data rows in all aspects, so: <pre><code>"COLUMN1","COLUMN2" -------------------^ this character has to be \n </code></pre></li> </ol> In all honesty, I think you could spend a week fighting with all of these nitty-gritty <code>BCP</code> and <code>BULK INSERT</code> issues, and still not have a perfect solution that doesn't require post-op actions (such as trimming leading/trailing <code>"</code> characters from certain columns). My recommendation: spend 20 minutes and write a parser in C# that will automatically correct these files - removing the header row, ensuring the right delimiters are in place, removing all the stupid <code>"</code>, etc. before SQL Server ever sees the file. Cleaning the file up will be a lot less hassle than the hoops you're jumping through now. I'm sure there are solutions to this but IIRC you've been wrestling with it for quite some time...
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POfirst data row skipped in import
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAaron Bertrand
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POfirst data row skipped in import
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.