Tuesday, March 20, 2012
Run saved DTS package in 2005
You do not have a saved DTS package in 2005. 2005 does not support DTS packages.
Shame on you for trying to decieve people!|||You need to make sure the DTS runtime has been installed.
http://msdn2.microsoft.com/en-us/library/ms143706(SQL.90).aspx|||Blindman -- must be
When talking about dts i was referring to the equivalent, guess that was to much logic for you to handle|||I have saved a DTS Package, in sql serv 2005. How do i run it ? I cant fiqure it out
Manually or scheduled?
In the BI Dev Studio you just right click to run. If you run as a job, then just choose the package when you set up the job step(s).|||Blindman -- must be
When talking about dts i was referring to the equivalent, guess that was to much logic for you to handleBlind leading the blind. You need to be clear, because you can access SQL 2000 database from the 2005 Management studio and even see a list of DTS packages, but you can't edit or run them.
Thus, the need for clarity...
Wednesday, March 7, 2012
Run a query that I have stored in a table cell
This is embarasing.
I'm creating a 500 line query from XML, CSV's, etc. and I can't fingure this out.
I'm building a very complex "SELECT" query and then shoving it into the [Select] column in a SQL 2005 table. I want to call a stored procedure that just "executes" that query and returns the results...
Any help would rock.
Gah, can't believe I didn't get it.
I was trying:
EXECUTE ((SELECT [Select] FROM [Item].[Filters] WHERE FilterID = @.FilterID))
And it needed to be:
DECLARE @.Select VARCHAR(5000)
SET @.Select = (SELECT [Select] FROM [Item].[Filters] WHERE FilterID = @.FilterID)
EXECUTE (@.Select)|||
I dont know if i have interpreted your query correctly but is this what you are looking for:
CREATEPROCEDURE [dbo].[uspMyDynamicQuery]
(
@.ColumnsASVARCHAR(400)--pass the columns in like field1, field2, field3 and etc.
)
AS
SETNOCOUNTON;
DECLARE @.SQLASVARCHAR(4000)
SET @.SQL= N'SELECT '+ @.Columns+ N' FROM tbl'
EXEC(@.SQL)
|||
Thanks for the reply :)
I have it working in the 2nd post. I basically did the same thing you did, but rather than build @.SQL, I just retrieve it.