anyone ever encountered this....i have a package which will execute fine manually but when i try to schedule it, it fails immediately (within the first second).i can even right click on the scheduled package and do "generate sql script" and then run that script and again, no problem. it just will NOT schedule.any ideas?
http://msdn2.microsoft.com/en-us/library/aa177009(SQL.80).aspx i need to schedule asp code execution using SQL Stored Procedure ...im not allowed to connect using Enterprise Manager is it possible in ASP and in case how?
Hi all, I want to make a job schedular in SQLServer 2005. That is i want to send email to users daily at 12:00 PM. how can i schedule using SQLServer Agent in SQLServer 2005. And i want to filter the users from user table. Please help me Thanks!
I have lots of DTS Packages that I am running manually daily and I am trying to create schedule all of those and all of them are failing. Some of those are accross domians,but the owner on both domains have same userId and password.
Any Idea why this is failing would be really helpful
I would like to import data via DTS from one db to another to run every half hour.What would be the easier way to do this?Should I setup a job to run every half hour?
If anyone could help with some suggestions , it would be appreciated.
When I try to schedule a DTS package which is an EXE it doesn't run. If I just run the DTS package it works fine. I have checked the permissions of the DTS scheduled package and made sure it had proper rights. SQL Server Services were started with the proper security rights. When I schedule the DTS package, it is being done on the Server, and not a workstation. Any ideas on why it will not run?...
Also, How do you schedule and EXE under SQL Server Agent Jobs. Even when I schedule an EXE that is not a DTS package it doesn't run...
I have almost completed a full project by myself which is soooo exciting. The last thing I need to do is schedule a job to run the query on a specific day and time. So how do I do this? It asks me for a command and I am not sure what I am supposed to enter in here.
Im trying to schedule a DTS package that I have created. When I right click on the package in Enterprise Manager and click on "Schedule" I get the options to set up the job to run on a schedule.
I fill out the time and click "OK". But when I immediately right click on the package again, all my settings are gone, and the defaults are back in place.
How do I know if the package will run- or if it did run?
I would actually prefer to run the job from a command line using a Scheduled Task... What would the syntax be? My DTS Local Package is named "IMPORT_DAILY_UPDATE"
I create a new in SQL Server Agent. However, When I click start Job at step, the first step start immediately,not the schedule I set. So How can do I make it to run at the schedule time?
Does Anyone know if there is a way to verify the SQL Service Pack Version on 7.0 on Windows 2000 Advanced server?
I'm getting this results for select @@version
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 1998 22:20:07 Copyright (c) 1988-1998 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 1)
I installed Service Pack 5 on SQL 7.0 successfully, but when I go back to run @@version, it gives me Service Pack 2 which is the old pack. Does anyone know why and had an experience with this?? Thanks wonderful people!!!
I have a cluster server, with SP3 coming out I wanted to upgrade the SP2 I have right now, when I start SP3 installation it starts and quickly exits from the program. DO I need to uncluster the server before applying SP3? or there is a way arround it?
has anyone had this experience before after we installed service pack 2 our jobs are taking about 10hrs, some run it says it's succesfull but it didn't update the tables.
I have installed service pack-1 on SQL SERVER 7.0 Standard Edition. After the pack is installed @@version is still showing 7.00.623 instead of 7.00.699 HELP !!!
Does anyone else have any concern about this Watson technology creeping in to SQL Server in SP3? I don't like it in Explorer and I'm sure not going to like it in SQL Server!
BTW, Forrest article about the new security patches at http://www.databasejournal.com/news/article.php/1475241 is in error, I think, when it refers to SP4.
Is the sql server 2000 service pack 3 worth applying to production database server or should I still wait. i do have sql 2000 service pack 2 on the server ?