Jeff Moden (5/24/2011)

---

Gosh, folks. I've not tried to import the data (yet) but the "Read Me" pointed out in the original posts seems to identify column requirements quite nicely....

what a pain that file is.

this is what i did:

i converted all teh damn unix LF to vbCrLf.

then i used this script...i had to tweak it a few times,...

indenting code is your best friend.

while there's no hard and fast rules, i tend to do something like this:

columns indented compared to the select

joins are indented from the FROM...

could it be users from the domain that are not explicitly added as logins? so if the domain group myDomain\Dev was added, people get in with no login?

so you'd have...

pretty sure it has to do with the import package defaulting to a 50 char field, and the data for example, on line 1284 is 54 characters in length.

"Beautiful Zion...

not sure it's possible...you need the backup to complete before you can determine it's size....

That makes me think it cannot be done before the backup is complete...unless it's based on...

ekta your example only works if an index has one and only one column in it's definition...otherwise it scripts two definitions...

also note there are different types of bar codes, so you need to know which style you need:

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...