if you use GROUP BY, then every column that is not using a SUM() or AVG() or other grouping operation MUST be in the GROUP BY Statement...so your query would...

you must create the tables with the PK's and FK's...otherwise what you stated....inserting 5 into the child table without checking that the 5 exists in the parent table could occur...that's...

it depends on the locks that the update and insert will demand.

if your update is fiddling with, say, a single row of data, then the update will get a shared...

i guess more information is needed...

nothing gets handled automatically for you as far as PK/FK's go....you might not be doing things in the right order of operation.

did you add new...

there is a real good artical called "calculating work days"[/url] by Jeff Moden here on SQL Server Central that explains the concept and also has a function at the end...

can you show us the execution plan when you run the update? that will tell us exactly what the update is doing, and allow us to offer suggestions like indexes...

there's a script contribution that would load the default trace into a table for review:

Load All 5 Default Trace Files[/url]

maybe that will help

there you go Jeff; Call Microsoft and tell them that the premiere RE-BAR avoidance specialist is offering to rewrite any of their 194 stored procs at the everyday low price...

very wierd;

I have half a dozen DotNetNuke installations either locally, for friends, or on my hosted web site;

if you are in as sa or admin you should see everything;

when i...

ok a few ideas;

first to be clear, there is no way to update the data "before" a select statement gets called.

While I know it's possible for the data to be...

what have you tried so far?

you can find all the modified dates and creation dates in sys.objects;

filter the type column for types like 'P' and 'FN', etc

sp_helptext gives you the...

you have to create a trigger for each table you want to audit. it's rare that you really need a trigger on EVERY table...just specific ones is more common.

look in...

readonly permissions?

stored procs only have EXECUTE permissions...

do you mean to read the text of procedure from sp_helptext procname,

or

permission to execute EXECUTE the procedure, but have only READONLY permission...

I'm assuming 's one specific table right?

restore the backup under a different name... once it'se you can investigate what data is missing, and check other tables for missign data as...

here's a step by step, using the DATEADD function, which is hte better way to tackle this i think:

as far as positive or negative, you'd want to handle that as...