Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Use a stored procedure to call xp_cmd and run a dtsx package

Posted on 2011-03-16
2
Medium Priority
?
435 Views
Last Modified: 2012-05-11
I created a stored procedure with the command below. I want this stored procedure to execute a dtsx package using xp_cmdshell. The procedure was successfully created but when i try to run it the query just runs, never finishes. The dtsx package works, i've used it many times using xp_cmdshell, so i figured it would work through a SP so that i can call it from an application. Here is how i'm calling it

use Forensicon_Max105
execute uspWorkTick

I have never used SPs before so please be clear when offering suggestions or questions.

Thank you.
-- ================================================
-- Template generated from Template Explorer using:
-- Create Procedure (New Menu).SQL
--
-- Use the Specify Values for Template Parameters 
-- command (Ctrl-Shift-M) to fill in the parameter 
-- values below.
--
-- This block of comments will not be included in
-- the definition of the procedure.
-- ================================================
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author:		Yaniv Schiff
-- Create date: 3/16/2011
-- Description:	Import SP WorkTick Data
-- =============================================

alter PROCEDURE uspWorkTick 
	-- Add the parameters for the stored procedure here
	@Path nvarchar(50) = 'c:\ImportWorkTickDB.dtsx'
	
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;

    -- Insert statements for procedure here
	print @Path

	exec Forensicon_Max105..xp_cmdshell @Path
END
GO

Open in new window

0
Comment
Question by:Yaniv Schiff
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 14

Accepted Solution

by:
Daniel_PL earned 2000 total points
ID: 35150238
Try changing line 35 :) :
 
declare @sql nvarchar(1000)
set @sql='exec xp_cmdshell ''dtexec /f'+' "'+@Path+'"'''
select @sql
exec sp_executesql @sql

Open in new window

0
 

Author Closing Comment

by:Yaniv Schiff
ID: 35151242
That worked perfectly!

Thanks
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question