check the data in ProductSuppliers.Margin; maybe the margin is stored as a percentage?

so maybe it should be < 0.35 instead of < 35.00?

also, check the datatype.. why are you comparing...

do you have an additional instance of SQL on that server? maybe the isntance is using that mdf and not the default instance?

if you

select * from master.sys.sysaltfiles

do you see...

Nice code Gianluca;

I see how if you are rounding up, it works perfectly; I added that to my snippets for future use, thanks.

also, the file path might have something to do with it; even with my windows login, I cannot write to the Root of the C:\ drive without "running as Administrator"...

yep, it's scripted for one specific database id:

exec sp_trace_setfilter @traceidout,3,0,0, N'60' -- AND DatabaseID = 60

it's from this non-obvious snippet:

set @intfilter = 60

exec sp_trace_setfilter...

piece of cake, it's only syntax.

the WHERE statement goes AFTER the output...not before it:

CREATE PROC CarProductionStateUpdate

@CarID INT,

...

wierd; do you have any filters in the trace script that might not be the same, you know, like filtering for a specific databaasename or dbid, and it doesn't exist...

Jason you are using C#.NET, right? why not take advantage of the typed data sets and the relations?

for example, In .NET i can add parent and child records to any...

As stated, there's a lot of concepts you don't seem to be able to grasp;

one of the ones that everyone mentioned that could help you turn this into a set...

if you sp_help YourProc name, what owner/schema is it? you get results like this?

sp_help sp_Test

Name Owner Type ...

...buth this random guy on the interwebz gave me the code to make this run faster ...what do you mean the numbers are off?...

I've been watching this one too...but the requirements scream "homework" to me, where the teacher wants you to use a specific set of...

the max value of the column, whether it's inserted by the identity() or not, is the max value of the data type...int, bigint, whatever type you decide.

an int is 2...

can't you just add to the WHERE statement to exclude items you don't want to include? like AND issqlrole = 0 or something?

yep Ninja's right; the key is the procedure usp_generate_purchase_order and the code you commented out ; whatever it is doing to a single set of parameters needs to be moved...