StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19315962
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-11T10:31:50.387
FavoriteCount
0
LastActivityDate
2013-10-11T11:17:44.710
LastEditDate
2013-10-11T11:17:44.710
LastEditorUserId
2067753
OwnerUserId
2067753
ParentId
19182785
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
EDIT, using ISDATE() makes sense for validation, change of approach. With respect to that conversion error, all I can assume is that some data doesn't meet some date/time 'rules'. With that in mind perhaps try something like this for discovery of those conditions. It's simplistic but may be helpful. Note you could do this as a count(*) first as I'm unaware how many records you are dealing with and won't say that this will be super quick. <pre><code>SELECT yyyymmddxxxxxx , CASE WHEN isdate( (yyyy + '0101') ) = 0 OR ( yyyy < '1960' OR yyyy > '2020' ) THEN yyyy ELSE '' END AS yyyy , CASE WHEN isdate( (yyyy + mm + '01') ) = 0 THEN mm ELSE '' END AS mm , CASE WHEN isdate( (yyyy + mm + dd) ) = 0 THEN dd ELSE '' END AS dd , CASE WHEN ( hh > '23' ) THEN hh ELSE '' END AS hh , CASE WHEN ( mi > '59' ) THEN mi ELSE '' END AS mi , CASE WHEN ( ss > '59' ) THEN ss ELSE '' END AS ss FROM your_table CROSS apply (SELECT convert(varchar(14), yyyymmddxxxxxx)) AS ca1 (int2str) CROSS apply (SELECT substring(int2str, 1,4) -- yyyy , substring(int2str, 5,2) -- mm , substring(int2str, 7,2) -- dd , substring(int2str, 9,2) -- hh , substring(int2str,11,2) -- mi , substring(int2str,13,2) -- ss ) AS ca2 (yyyy,mm,dd,hh,mi,ss) WHERE ISDATE(convert(varchar(8),int2str,112)) = 0 OR ISDATE( (hh + ':' + mi + ':' + ss) ) = 0 OR ( yyyy < '1960' OR yyyy > '2020' ) -- arbitrary, ignore of change to suit ; </code></pre> <a href="http://sqlfiddle.com/#!3/9ab73/1" rel="nofollow">http://sqlfiddle.com/#!3/9ab73/1</a> output is like this: <pre><code>| YYYYMMDDXXXXXX | YYYY | MM | DD | HH | MI | SS | |----------------|------|----|----|----|----|----| | 99990410123456 | 9999 | | | | | | | 20149910123456 | | 99 | 10 | | | | | 20140499123456 | | | 99 | | | | | 20140410993456 | | | | 99 | | | | 20140410129956 | | | | | 99 | | | 20140410123499 | | | | | | 99 | | 20140231123499 | | | 31 | | | | </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConverting a YYYYMMDDXXXXXX into a workable Date
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USUsed_By_Already
UserOwnerUserId
1. USUsed_By_Already
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.