New answers tagged best-practices
This is not database administration, this is data modeling. Very different disciplines. I'm guessing your main entity is Simulation and the tables you list describe it. You don't show the structure or content of these tables so the following is based on conjecture. Measurement looks like it could be a list of measurement types: temperature, flow, particles ...
Always try to think ahead, use table and field names that are self documenting (self-explanatory) whenever possible. Don't just string a bunch of letters together and assume the person to come behind you would have any idea what they're looking at. Naming things in this matter also makes it much easier to see what results your query is returning.
My preference would be to name the columns like final_flow_rate__value, etc, since value by itself can easily become very confusing if there are multiple columns named that. Take for instance: SELECT measurement.value sampling_rate.value first_draft_flow_rate.value second_draft_flow_rate.value final_flow_rate.value FROM ...
Instead of changing the names of individual tables, I would recommend using schema names to denote the different types of users. For instance: Admin.Users Reader.Users Approver.Users Using Schemas in this way allows a more flexible method for controlling access since you can assign rights by schema instead of at the individual table level.
We have lots of servers with 4 cores and some with 8 cores. I recommend with such few cores that parallelism (MAXDOP) be set to 1 so to avoid waits on CPU (and also timeout issues) for users of OLTP systems. For OLAP or reporting servers, with such few cores, I recommend setting MAXDOP to 2 and setting Cost Threshold to 30 (this may be higher or a bit lower ...
He seems confused. Using the same value from a local variable should be no different to using it from an input parameter. Is your colleague getting the wrong end of the stick with regard to using parametrised queries (sometimes called prepared statements) instead of full ad-hoc SQL? For example: resultSet = dbconnector.getRS('EXEC sp_foo_GET ...
Top 50 recent answers are included