Viewing 15 posts - 2,281 through 2,295 (of 2,636 total)
I wonder if this custom task will be updated to work with SSIS in SQL Server 2005. I'd be cautious about using it in packages that will be run in...
August 10, 2005 at 2:25 pm
As far as I know, there still is no way to do this. The password is encrypted within the package id in sysdtspackages. It's not stored in plain text anywhere.
Greg
August 10, 2005 at 1:24 pm
Are you working with 3 tables aliased as p, a, and m? I don't understand what tabl a is for.
If that was a typo and you're really dealing with only...
August 4, 2005 at 2:59 pm
James,
As Remi suggested, restore msdb to another instance. Open the package, click on Package, Save as..., and save it back to the original server. There's also a utility at DTS.com that works well:
August 4, 2005 at 9:34 am
Are you using the 'Copy SQL Server Objects' task? If so, are you using the default option to import database users and roles? Try unchecking that option and see if the DTS works. ...
August 3, 2005 at 2:39 pm
August 2, 2005 at 10:37 am
In the Query Analyzer Object Browser, right-click on the table, choose 'script object to new window(or file, or clipboard) as insert'.
Greg
August 1, 2005 at 1:22 pm
To answer the vice versa part of the question: a DTS package can execute a job also using sp_start_job.
Greg
August 1, 2005 at 1:18 pm
You want to insert the SQL statements as a string into a varchar(2000) column of a table? Try replacing all the single quotes with double quoutes then wrap the entire...
July 27, 2005 at 3:12 pm
Create a unique constraint on the column.
July 26, 2005 at 5:26 pm
Does your destination table in SQL Server have primary key contraint or a clustered index on the column? If not, the rows won't be ordered by the column.
I don't...
July 26, 2005 at 11:04 am
Found this in KnowledgeBase:
http://support.microsoft.com/default.aspx?scid=kb;en-us;890637
Hope it helps.
Greg
July 22, 2005 at 10:45 am
My colleague says he didn't have the problem you described.
Sorry,
Greg
July 21, 2005 at 2:27 pm
I've seen that message when using 'memory tables' i.e. local temporary tables. Try changing the stored procedure to use global temp tables (## as the first characters of the name). ...
July 21, 2005 at 1:05 pm
We are using it, though I didn't install it. I'll ask my colleague who did the install if he had similar problems.
Greg
July 20, 2005 at 5:24 pm
Viewing 15 posts - 2,281 through 2,295 (of 2,636 total)