SQL Running process

[Slingki]

Hi guys

Im trying to run a SQL query that will run at the end of every week, My thought process will be to build an *.exe file, and from the scheduled tasks on windows, execute that file.

Is my thought process correct, or is there a way to todo it from SQL server?

Thanks
D

[masdi2t]

Hi guys

Im trying to run a SQL query that will run at the end of every week, My thought process will be to build an *.exe file, and from the scheduled tasks on windows, execute that file.

Is my thought process correct, or is there a way to todo it from SQL server?

Thanks
D

first of all, u have to create a new package contains ur SQL query (using DTS), 'n the next step is creating Jobs to execute ur package.

rgds,
masdi2t

[cbellizzi]

I guess you need to be a little more detailed in what you’re trying to accomplish. What type of information are you looking to gather? What platform are you on 2000 or 2005 or SQL7? There are different tool sets for all the platforms. I'm not sure that you would want to externalize your process.

[Slingki]

Ok here is my thought process.

Im running SQL 2005, which will hold a table of news articles posted by a user...
But those articles will not stay in the database for more than a week, so say every Sunday the script??? will execute and all the records with the thats dates are 7 less than the current day will be taken out the table in inserted into another table called archives... Do you think this is the correct way of doing it or should I look at another solution.

all the general functionality I have done using ASP, But I don't want someone to go every sunday and archive all the articles.. so in my previous post is my thought process.

Hope you can help!!

[cbellizzi]

I would just run a SSIS package that would insert the values into another "archive" table and delete them from the current. Schedule it to run as a job at a certain time. I wouldn’t complicate things but that’s me Mr. Simple

[Seun Ojo]

First as for the problem u r tryin 2 solve; ur approach is not d optimal....or so i think...

i would have added anoda column(say Archive) to d table dat contains d articles(lets say Articles Table)....The Archive column will have a bit data type; a value of 1 means d article is archive(as in: Archive? Yes! where yes is 1) n 0 means Not Archived....The default value will be 0, of course, for ds column

So u can write a T-SQL codes dat will check any article whose presence on d table exists 7 days...for doz record u will set deir their 'archive value' to 1.

u will den do job scheduling(From Ms Sql Server: tools>Job scheduling)...their u specify database n copy n paste d t-sql statement u wrote (make sure to select T-SQL Command as type of command to execute)...u den go on to specify d frequency on ol dat...

i suppose u can write d t-sql code....? let mi no if cant?

op dat solves d problem...?