For the XML option, I have attached 3 SQL scripts based on the previous example of a simple Food table.

The scrQuery_Food script is a generic query - you can pass...

One of the first things I was ever taught in SQL was writing a Select statement that returned other formatted SQL statements using data from the original Select. The following...

Not sure of the advantage of a single pass-through query that you change as required - personally, I would still create a separate query for each SQL script, then you...

Looking for possible occurrences of UPDATE, DELETE, ALTER, etc. in a query parameter could get very lengthy and won't cater for new features released in later versions of SQL.

You can...

If the possible values are limited it may be better to use a ComboBox instead of a TextBox, then you can use a SQL query to populate the ComboBox and...

My 2c ...

I'm not a DBA. I come from a development background, moving in more recent years into a SQL role (database design, rather than the server management). I still...

I've also seen it done both ways, and of course each has advantanges.

Personally, I prefer a single table for simple code/description lists (or two tables, as you suggested) and have...

Mr. Newbie (10/29/2009)

I like this idea, so I will remove all of the tools attribute in the request table. But where will I store the info on each transaction?...

I would lean towards keeping the different tool attributes out of the requests/returns tables, otherwise you may need to add a lot of extra validation to ensure that appropriate values...

You will probably need to create multiple queries to build up to the result that you want.

I setup a table with your values, then 3 queries; one to retrieve the...

Quite agree, however, the difficulty is in finding someone with enough technical skill to lead the grunts to ensure they don't run off on wild fancies, and at the same...

You could add a "sort" column to your temporary table - like an Identity column that simply generates a sequential number, incremented for each row inserted into the table.

You can...

I have seen both, and generally prefer the MUCK option - it may not be best practice, but I dislike having 100 tables with a handful of rows each and...

The simple ideas are often the best - storing both UTC and local time, or the difference between them, may not be the ideal model but there has to be...

I haven't had a lot of experience with UTC dates/times and what is considered to be good design practice, but do have a few comments based on a document management...