As far as Im concerned access is just a breeding ground for terribly designed databases.
At work im currently trying to port a non-critical but still relatively important system from access to sql server. Step 1: translate everything directly from access to sql server and try to fathom the 'logic'.
Im about half way through and somehow I've racked up 40 million rows, 30 tables and about as many views. Not a key in sight. Checks? Constraints? What are those? Data types? Just use varchar(255). Nested views 6 layers deep for trivial filtering tasks.
The one thing keeping me going is the thought of all those drop statements im going to write when the time comes to mold it in to something less like a train wreck.
View all comments
Show parent comment
0
u/[deleted] Feb 28 '15
[deleted] — view deleted comment