It doesn't look too bad. I would highly recommend you NOT name your primary key ID in every table. You should give it a descriptive name. ListID for example. Otherwise you will be committing what I consider a major sin (A column name should remain consistent throughout the entire database). I am not sure what the TaskNameList table is for. The first 3 tables are a pretty straight forward parent/child/grandchild. The relationship is 1:* so there is no need for the the last table. What would help even more would be to have ddl along with constraints. Then we can get a better idea of what you are doing.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/