and there it is. some how i think

that will completely resolve the issue.

going to test this out around lunch time today.

thanks lance!!

ken... many thanks!

lindss...

not really. i i'm only responsible for getting the data

across in the quickest way possible, and can't really

make changes to the columns, or the data....

perhaps i should drop all keys/constraints etc prior

to the import

is it possable capture all

different types of keys prior to drop, and then

recreate them 'exactly' as they were after the

import is...

not really just exported it with bcp using

the -n switch is about it.

out with:

bcp pubs..authors out c:\authors.bcp -n

then importing it with the following:

bulk insert pubs2..authors from 'c:\pubs-authors.bcp'

tried this real quick on an export from authors table, and

upon inserting it into another db like pubs2 with bulk insert

i get the following:

Bulk insert data conversion error (truncation)...

Ten Centuries posted this...

------------------------------

Personally I prefer to flush out a table and repopulate in preference to DROP/CREATE.

For big import jobs I tend to follow the procedure below.

...

excellent idea!! this is awesome!!

question is... can this be automated via script

maybe within a 'bulk insert' ??

so just be sure though... is it possable capture all

different types of keys...

is no problem. thanks for all your help any way

yikes... i may be in over my head on this one.

i thought it could be a simple one-line script

or some thing.

all this just to get the last 4 wks from...

[DATEFIELD]column is the following:

Type: int

Computed: no

Lenth: 4

Prec: 10

Scale: 0

Nullable: yes

TrimTrailingBlanks: n/a

FixedLenNullInSource: n/a

Collation: null

this is the column definition... does this help at all,

i mean is this useful?

i'm getting the following error:

Msg 8115, Level 16, State 2, Line 5

Arithmetic overflow error converting expression to data type datetime.

is there some thing i did wrong?

so this can be automated?

i mean if i build this into a job, do i have to go

back and edit the (set @d = 'today') every time?

thanks in advance.

yeah... the problem here is that when you go to the 'Jobs' category under

the SQL Agent, and goto All Tasks, then generate a script for all jobs,

it's not like it...

cool... thanks! i knew it was out there some where.

one other question... i'm reading mixed reviews

on the process.

has there ever been any incomplete issues with this?

sp_msforeachdb 'sp_addrole ''role_name'' '

where...

right... but question remains on how to

add a single role to all databases at once.

thoughts?