could this be realted to the parameter sniffing issue that sometimes occurs...that is exactly the symptom...works fine with static value, very slow with variable... search for parameter sniffing  and see...

as i remember, the trick is to select the TOP N  of a sub select:

select TOP 12 empid,empname from emp order by empid  contains all teh records you want, so...

here's an example; this is getting everything out of a table in a loop, and should give you the framework you are looking for:

Private Function ExportBlobs()

    Dim ConnObj...

yes, and that's exactly what we do in our shop...we make multiple ERD's, each related to following a specific flow of data...one for product and it's attributes, another for orders...

ok poking around the registry, i found this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\NUMBER_OF_PROCESSORS

now to read that from each machine on the network , i would simply create a program to read that key...

that registry entry i found is not accurate, you are right...my home machine, which is just a single processor AMD64 has a registry entry of EIGHT processors for that value...I'll...

there may be other ways, but i found this snippet on sqlteam:

-- Get the number of processors that the server has

declare @NumProcs int

EXEC master..xp_regread

  @rootkey = 'HKEY_LOCAL_MACHINE',

  @key...

i just tested this, and it looks like you can see the execution plan;

i made a crappy proc, and tested it with encryption and without; both times i could see...

Sergiy's idea is exactly what we suggested for someone else to do:

 below i'm pasting a function that will create a value AA001 thru ZZ999 (675999 values max before this function...

good luck; it's been a while since i fiddled with access, but i remember access 2000 had a 255 column limit; maybe the more updated version might not have that...

i wrote this a while back:

it scritps out all PK, Uq and regular indexes. remove the top 100 to get all results, this can be a HUGE resultset, depending on...

i see errors like this when the source file is not formatted perfectly...for example, if you think the file is comma delimited, but a COMPANY column has a a comma...

I consider it a bad practice to insert summary data into another table...it is very, very possible the data could be out of sync.

you should simly use a VIEW instead.

CREATE...

i would not let a non-dba force me to use an unfamiliar product just because someone wants a lot of columns in a table...I would stick with a product i...

lots of different scripts to do this in the scripts contribution area; search for "compare" and youll get results like these: