sql scripts

i have a script that updates a field in the table.
i want to break the script into 4 parts.
how do i call the script one after the other without using a ssis package?
package_monkeyAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
jogosConnect With a Mentor Commented:
Split your script in 4 and then you have (besides running it in a sql-window) different options

Sql*agent
http://databases.about.com/od/sqlserver/ss/sql_server_agent_3.htm

SQLCMD
http://msdn.microsoft.com/en-us/library/ms162773(v=sql.90).aspx
0
 
Matthew KellyCommented:
How are you calling them now?

Generally, you could make them stored procedures, and then just have one script call each procedure.

Lots of examplese of stored procedures here: http://msdn.microsoft.com/en-us/library/ms187926(v=sql.90).aspx
0
 
package_monkeyAuthor Commented:
i have a package that executes sql tasks, it creates a  temp table.
next temp table is populated with the the values from 4 fields from the production table.
i update the table with another temp table which is created using inserts from the excel sheet.
then i use inner join to update the production table using the updated temp table.
my question is how do i break the scripts? i do not want to run the whole sucker as one script.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Matthew KellyCommented:
The four scripts you want are:

1. Scripts

Creates a  temp table.

2. Scripts

Populate temp table with the the values from 4 fields from the production table.

3. Scripts

Update the table with another temp table which is created using inserts from the excel sheet.

4. Scripts

Use inner join to update the production table using the updated temp table.
You then want the single SSIS package you have to execute all four scripts in order when called?

To do that, the best method is to create four stored procedures, each one doing one step of the above tasks; then have the SSIS package call each of the stored procedures. You would also be able to call the stored procedures manually one at a time without the package as well.

Is it timing out? Is that why you want to break the scripts up?
0
 
package_monkeyAuthor Commented:
i do not want to  run it in a one swing, as so many rows are being inserted and updated.
i do not want to cause any problem down the pipeline.
0
 
package_monkeyAuthor Commented:
it is a one time update. that is why i do not want to do it as a package or as a stored procedure.
0
All Courses

From novice to tech pro — start learning today.