When you are writing xUnit tests you are in certain ways trying to make sure that the test breaks when the code that is being tested changes the assumptions you made when writing the Test and Production code.
Some time ago I wrote about what it means to do database testing.. more I think about this and having had some strange situations recently I want to add more to the list of things we should be testing.
Many IT organizations I have seen have groups of specialists, typical are UNIX Group, DBA group etc.
In development mode you don't want to worry about which table goes into what Tablespace in production as it complicates development environments. The production DBA's want to have their input and control over deciding what table goes into what Tablespace. To allow for this I used a mapping scheme as shown below.
In any greenfield application (existing production application is a topic for
another post). When you design table(s) lets say you have Item and Manufacturer
table as shown below