Viewing 15 posts - 691 through 705 (of 2,636 total)
Try granting VIEW DEFINITION permission to the users in the database.
November 5, 2008 at 9:21 am
I haven't heard this is true and can't find any confirmation, even with a Google search. I kind of doubt that SSIS could use a binary .dmp as a...
November 4, 2008 at 9:52 am
To tell the truth, I haven't figured out how to give a developer access to DTS packages in SQL 2005. As for jobs, check out the SQLAgentReaderRole database role...
November 4, 2008 at 8:58 am
Good point, Ed. I use the DTS editor a lot since we still have many DTS packages in our SQL 2005 instances. Almost all of our production packages...
November 4, 2008 at 8:51 am
The SQL Server Upgrade Advisor can give you a list of things that will need to be changed to upgrade a DTS package to SSIS. If you still have...
November 3, 2008 at 10:30 am
Hi Rem,
Debug is only active for a project. It's disabled when you just edit a package file. Have your colleague create a new project then add the package...
November 3, 2008 at 10:10 am
Save the package as a file then, in SQL Server Management Studio Object Exporer, expand Management, Legacy, right-click "Data Transformation Services", and select "Import Package File".
November 3, 2008 at 9:45 am
Connections are part of the package and the package information is stored as binary data in msdb.dbo.sysdtspackages, so there isn't a way to get the information with T-SQL. The...
October 31, 2008 at 10:26 am
I might not understand your question, but DTS packages are only stored in the msdb database.
October 29, 2008 at 5:17 pm
Since you've created the SQL 2005 database with different table schema than the SQL 2000 database, you can't use backup and restore either. SSIS or DTS are the methods...
October 29, 2008 at 3:33 pm
Yes. I get it all the time and ignore it with no problems.
October 29, 2008 at 3:22 pm
You'll need to set the protection level for each package as you edit and save them in BIDS. Then you provide the password in the ExecutePackage tasks in the...
October 28, 2008 at 4:41 pm
It depends on who will be executing the packages in production. If you use any of the ..UserKey protection levels, you'll be the only one who can execute them....
October 27, 2008 at 4:50 pm
The job must be connecting to Box2 via a Linked Server which maps the SA login on Box1 to the SA login on Box2 with the password for the Box2...
October 27, 2008 at 12:20 pm
It also occured to me that if you have Express Edition, SQL Server Agent isn't included.
October 24, 2008 at 9:08 am
Viewing 15 posts - 691 through 705 (of 2,636 total)