50 years, as opposed to SQL 2008, which was released....was it August 2008.

50 years = 6 months...hmm... hmmm... sorry, im just trying to see whats up with that statement....

Im not a writer, im not a publisher. i dont have better ideas.

I am a consumer though. and i spend my hard earned cash on these books.

Whats the point...

i recieved a reply from MS on this, to my bad review on amazon!

here's what they said:

It often takes at least 8 months to produce a book, from the time...

yea its the Microsoft press 70-432 Microsoft SQL Server implementation and maintenance self paced training kit by Mike Hotek. ISBN: 978-0-7356-2605-8

Here it is on amazon:

http://www.amazon.com/MCTS-Self-Paced-Training-70-432-PRO-Certification/dp/0735626057/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1235505069&sr=8-1

ive also done...

im sorry to bump this up, but having tinkered with it for hours on end, and googled it a lot i still cannot see why the column datatypes are a...

is there a need to backup the tempdb really?

On my laptop the sql server service was running under Network Service. I know not its not the way it should be, but its not a live production system, just...

I cant test now as i dont have my laptop home with me, but thats strange, as the folder that i created the datbase in was created at the same...

Cool, careless of me to miss that in BOL. thanks.

Ok. so what im doing now is this:

alter database test_DB

set offline

Go

alter database test_DB

modify file

(

name = test_DB,

Filename = N'C:\DatabaseRestoreTest\Files_location\test_DB_temp.mdf'

)

GO

alter database test_DB

modify...

Here is some further information to help get my issue across more clearly.

here is an image of the table, as seen via the OLE DB Destination in SSIS:

http://s78.photobucket.com/albums/j87/schmintan/?action=view&current=Output_Columns.jpg

You...

you were correct. In the connection manager, i had not set the flat file column sizes correctly. once i done this, the flat file source was correct.

i have this joined...

but from my previous post, i can see this is pc specific. i get the odd charachters from the server the database is located on, but running the same query...

Update on this:

It seems that when i query teh data using SSMS installed on the server i expirience the problem where i cant see asian charachters, however if i query...

yea, any columns in question are nvarchar

i cant see how writing this as a co-related query, il be able to work out the debit amount minus the credit amount though.