RE: Importing a DTS from Sql 2000 to Sql 2005
- From: "itsdeshpande via SQLMonster.com" <u50476@uwe>
- Date: Tue, 07 Apr 2009 08:55:14 GMT
Hi DC,
Thanks for the reply.
Well, my problem solved; but I think its just one of the cause of this kind
of error. I found that the TempDB and the user DB that I was working on were
not set to Autogrow and also there was a bit of disk space issue too. I set
them to autogrow and cleared some space on the data and log drives of these
DB's and I could get the package working.
In another environment, they fixed it by adding the service account running
the package into the SQL Logins explicitly (meaning, though this account was
a local admin; inspite of that) of that server to which this 2000 DTS package
was connecting.
You may want to try these..
Thanks,
Manoj Deshpande.
GC wrote:
Hi Manoj,
Sorry for the delay for answering to your message but I stop for a while
working on this issue. I decide to learn more about security and context to
understand what is exactly happening.
Thanks for the hint.
I tried both of your suggestion and still does not work.
I am searching a way to log everything of what is executed by the job to see
exactly where it fails and for what reason.
So I'm still working on my problem.
I am not an expert so thats is why it is long to find the problem :)
What about you did you find something on your side?
Thanks in advance and have a nice day!
HI GC,[quoted text clipped - 22 lines]
Thanks in advance
--
Message posted via http://www.sqlmonster.com
.
- References:
- Prev by Date: RE: Retrieving Data based on parameters entered in Destination Dat
- Next by Date: Re: Sheduling DTS-Packages in SQL2005
- Previous by thread: RE: Importing a DTS from Sql 2000 to Sql 2005
- Next by thread: Log Error question
- Index(es):
Relevant Pages
|