Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Managing DTS packages - Editing, Scheduling, and Viewing Package Logs


Managing DTS packages - Editing, Scheduling, and Viewing Package Logs

Author
Message
Haidong Ji
Haidong Ji
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 60
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/hji/managingdtspackageseditingschedulingandviewingpack.asp



jG
jG
SSC-Enthusiastic
SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)SSC-Enthusiastic (137 reputation)

Group: General Forum Members
Points: 137 Visits: 14

Some questions on your article.

If you create a generic SQL ID for the developers, how do you know who changed what.

Now that they all have the same ID. It makes is impossible to specify which devleper gets DBO rights to there DB they are working on.

Did you encounter any of these issues and how did you overcome it?




-JG
SQLGuy64
SQLGuy64
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 291

My experience with using sp_reassign_dtspackageowner in a Windows authentication mode environment is that once a developer saves a change to the package, the package reverts back to the original owner.


Shiva kumar-275367
Shiva kumar-275367
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 7
i have imported a DTS package from one sql server to another. the source server uses windows authentication and the destination uses sql authentication.
when i transferred the package, the owner id in the destination still shows the windows id of that of source server login. due to this i believe i am unable to edit it.
any suggestion..on how i can edit and save it.
thanks
-shiva
SQLGuy64
SQLGuy64
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 291
Have you tried to edit and save it? How about resaving package with another name?
debrucer1
debrucer1
SSC Veteran
SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)SSC Veteran (258 reputation)

Group: General Forum Members
Points: 258 Visits: 136
good article; but sometimes DTS packages seem more "mystic" than this... scheduling, security context, proxy accounts, service accounts... thank you Bill Gates... unfortunately, it doesn't seem that SSIS is any better. But, thanks for repeating the article... good job.

Thanks,

David Russell
Oracle Since 1982
SQL Server Since 1998
Allen McGuire
Allen McGuire
SSC Rookie
SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)SSC Rookie (34 reputation)

Group: General Forum Members
Points: 34 Visits: 551
I really disagree that SQL authentication is better than Windows - I can make a laundry list as to why, but I don't have the time. I just can't imagine someone advocating Mixed Mode or SQL authentication.


Kindest Regards,

Allen McGuire
madtownlounge.com
melvin carter-454287
melvin carter-454287
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 23
jG (2/4/2005)


Some questions on your article.

If you create a generic SQL ID for the developers, how do you know who changed what.

Now that they all have the same ID. It makes is impossible to specify which devleper gets DBO rights to there DB they are working on.

Did you encounter any of these issues and how did you overcome it?


I'm wondering the same thing is there some SQL/stored procedure that can be run on the database to get a history of who made the change.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search