I believe this is my problem. The following is part of the error message.
TNS:listener could not resolve Service_Name given is connect descriptor. Error Source: Microsoft OLE DB Provider for ODBC drivers.
I am not sure why the listener could resolve the service name when I run it manually...
This article confuses the matter more for me. It says that in SQL 2000 (which is what I am running) that the job is run under the security context of the owner of the job. The owner of the job is a member of the sysadmin group and should be able run anything. I am not sure where to go from here.
I have a DTS package that is scheduled to run each night. The job fails in SQL Agent. I can execute the package through Enterprise manager and also run the job as well without error. Any ideas as to why I can manually run it but it fails when run on schedule. One other interesting note, in...
The backup copy shows the table as blank. It overwrote the existing media. Since there was no data in the table it overwrote the backup with data with the table that has no data. I hope that makes since. I am running sql server 7.0. Yes I am the sys admin on the server. Any ideas?
No backup the table is only a week old and the first backup was set to run last night. Hince backup without the data. I do not truncate the log file. Is there any way or am I screwed?
Do you know if the lumigent software requires a backup to perform the undo commands? I do not have a backup and the evaluation version only allows attatchment to the northwind database. I hate to spend $400 if it is not going to work.
I have accidentally ran a Transaction to export objects to the wrong database. In doing so I replaced a table that already existed with around 4000 records in it. Is there any way to do a roll back or recover from the .ldf file? I do not have a good back up of this database. I am in big...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.