Showing posts with label company. Show all posts
Showing posts with label company. Show all posts

Sunday, March 25, 2012

DTS Permissions

We have a DTS package that was created and saved by
someone who is no longer with the company. How can we
convert this DTS package to a valid ID? ThanksHi Natalie
I am reviewing your post and our community members provide some good
suggestions to your problem. Have you try these methods? Do they resolve
problem? If you still have any questions about it, please feel free to post
message here and we are glad to help!
Looking forward to hearing from you. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.sqlsql

Monday, March 19, 2012

DTS Package Owner

I have to modify the DTS package owner that is displayed in the local
packages view, the current owner no longer works for the company so I need
to reassign ownership. I am not a sql expert by any means.
Can anyone help me with this?
It is SQL Server 2000 sp4 running on Windows 2003 sp1.
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
Paul - please take a look here: http://www.sqldts.com/default.aspx?212
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||This is what I was looking for.
Thanks
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ulsvIajEHHA.992@.TK2MSFTNGP03.phx.gbl...
> Paul - please take a look here: http://www.sqldts.com/default.aspx?212
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

DTS Package Owner

I have to modify the DTS package owner that is displayed in the local
packages view, the current owner no longer works for the company so I need
to reassign ownership. I am not a sql expert by any means.
Can anyone help me with this?
It is SQL Server 2000 sp4 running on Windows 2003 sp1.
--
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.Paul - please take a look here: http://www.sqldts.com/default.aspx?212
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||This is what I was looking for.
Thanks
--
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ulsvIajEHHA.992@.TK2MSFTNGP03.phx.gbl...
> Paul - please take a look here: http://www.sqldts.com/default.aspx?212
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

DTS Package Owner

I have to modify the DTS package owner that is displayed in the local
packages view, the current owner no longer works for the company so I need
to reassign ownership. I am not a sql expert by any means.
Can anyone help me with this?
It is SQL Server 2000 sp4 running on Windows 2003 sp1.
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.Paul - please take a look here: http://www.sqldts.com/default.aspx?212
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .|||This is what I was looking for.
Thanks
Paul Bergson
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ulsvIajEHHA.992@.TK2MSFTNGP03.phx.gbl...
> Paul - please take a look here: http://www.sqldts.com/default.aspx?212
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

Wednesday, March 7, 2012

DTS Package

Hello everyone,
I am wondering if anyone can shed any light on a DTS issue that I am
facing. At my company we are using multiple DTS packages to extract
data from a 3rd party database using their ODBC driver. Every so often
a couple of the DTS packages fail - which can prove to be a real pain -
as I and a colleague have to check these processes around 7am every
morning (becuase some of the packages can take an hour + to complete)
to ensure that they have all worked as expected.
Now, when a DTS package fails I am sent an e-mail notification from
SQLServer.
E.g.
JOB RUN: 'PurchaseControl' was run on 07/06/2006 at 06:00:00
DURATION: 0 hours, 7 minutes, 46 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 64
(PurchaseControl). The last step to run was step 1 (PurchaseControl).
This is OK as it tells me the package that fails. However, I cannot see
why it failed, there is no runtime information regarding the error that
occured. Now, if I run a DTS package manually through SQL Server 2000
Enterprise Manager and a step in the DTS package fails it tells me
why...
E.g.
[Kerridge][KISAM ODBC Driver]error reading pkt body
Is it possible to obtain this type of information from scheduled DTS
packages, so that I can examine what are the common problems within the
packages?
I'd really, really appreciate help on this one, if anyone can spare the
time.
Thanks in advance,
Craig.Hi Craig,
Yes, within the package properties you have a logging tab where you can set
the package to an error file.
Ray
"crgsmrt@.googlemail.com" wrote:

> Hello everyone,
> I am wondering if anyone can shed any light on a DTS issue that I am
> facing. At my company we are using multiple DTS packages to extract
> data from a 3rd party database using their ODBC driver. Every so often
> a couple of the DTS packages fail - which can prove to be a real pain -
> as I and a colleague have to check these processes around 7am every
> morning (becuase some of the packages can take an hour + to complete)
> to ensure that they have all worked as expected.
> Now, when a DTS package fails I am sent an e-mail notification from
> SQLServer.
> E.g.
> JOB RUN: 'PurchaseControl' was run on 07/06/2006 at 06:00:00
> DURATION: 0 hours, 7 minutes, 46 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 64
> (PurchaseControl). The last step to run was step 1 (PurchaseControl).
>
> This is OK as it tells me the package that fails. However, I cannot see
> why it failed, there is no runtime information regarding the error that
> occured. Now, if I run a DTS package manually through SQL Server 2000
> Enterprise Manager and a step in the DTS package fails it tells me
> why...
> E.g.
> [Kerridge][KISAM ODBC Driver]error reading pkt body
> Is it possible to obtain this type of information from scheduled DTS
> packages, so that I can examine what are the common problems within the
> packages?
> I'd really, really appreciate help on this one, if anyone can spare the
> time.
> Thanks in advance,
> Craig.
>|||rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>
Hi Ray,
Thanks for that. However, I cannot appear to locate this 'logging tab'.
Would you mind telling me where to locate it. The closest item I have
found is on the 'Notifications' tab in the Management>>Jobs section.
However, I do not believe this is what you are referring to.
Regards,
Craig.|||rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>
The information that gets dumped into the Event Log is just as useless
too...
SQL Server Scheduled Job 'PointOfSale'
(0xE2A9D65E6F5BB04C9C6116CE1F07AA65) - Status: Failed - Invoked on:
2006-06-06 03:00:02 - Message: The job failed. The Job was invoked by
Schedule 61 (PointOfSale). The last step to run was step 1
(PointOfSale).|||Thanks Ray,
I've found it already.
Craig.
rb wrote:
> Hi Craig,
> Yes, within the package properties you have a logging tab where you can se
t
> the package to an error file.
> Ray
> "crgsmrt@.googlemail.com" wrote:
>

DTS or SSIS

I worked mainly on informatica , butmy company want me develop a datwarehouse using SQL Server.Presently they have SQL Server 2000. They want the first phase to be on 2000 using DTS and then subsequent phases in 2005 SSIS.

Can someone help in answering my queries.

1. Will I be able to run 2000 DTS in SSIS.

2. Which one is easier DTS or SSIS. I have come to know that SSIS is like informatica and no need to right big big stored procedure as we do in DTS for ETL.

3.If I make a part of Datawarehouse in DTS and the other in SSIS, will everything work.

4.If suppose i have shared dimension "X".in the first phase it is populated by DTS and in the 2nd phase can i also polulate by SSIS simultaneously.

1 Yes, but it is really a backward compatibility thing. SQL 2005 includes the ability to run DTS packages, but there is no effective upgrade path for DTS packages to SSIS packages. I generally advocate re-writing DTS as SSIS to get the benefit.

2 SSIS, unless you have a big DTS mindset to overcome. A little effort up front to get your eyes open to the tools available, and it should be easy going forwards

3 Yes probably, but just sounds wrong as the two are so different. Ongoing maintenance for a start would be horrible because it means support staff always need to know two technologies.

4 Yes, if we are talking about the tables, perfectly possible, it is after all just a table, so you can do what you want.

|||

I generally agree with Darren on the answers to your questions.

I would like to add a little comment though. Do you have any idea when you will be able to start working with SSIS? If you plan to move to SQL 2005 anywhere soon, I would strongly advise _not_ to start in DTS. As Darren states, if you have a DTS mindset, SSIS probably gets more difficult te learn. Besides, you will end up using two ETL tools. So you need to maintain your ETL using two tools, need the knowlegde of both...

Besides, you can use SSIS and still have a SQL 2000 datawarehouse. Just run SSIS on a separate server, and leave your source and DWH databases running on SQL 2000.

Regards,

Pipo1

|||2. DTS is "easier" - but scripting sucks (activeX only without any good designer). On the other hand i still write Stored Procs in SSIS - nothing compares to good ol' SQL

Go with SSIS if possible - it can populate SQL 2000 database. If mandated by management to use DTS - theres not really an easy upgrade path for the packages - IMHO - all Dts packages need to be rewritten (e.g. activeX scripts, Data sources in SSIS have datatypes etc.)

3. Mish & mash usually tends to be a headache|||

Kind of repeating what other people have said but nonetheless....

Ag_dwh wrote:

I worked mainly on informatica , butmy company want me develop a datwarehouse using SQL Server.Presently they have SQL Server 2000. They want the first phase to be on 2000 using DTS and then subsequent phases in 2005 SSIS.

Can someone help in answering my queries.

1. Will I be able to run 2000 DTS in SSIS.

Yes.

Ag_dwh wrote:

2. Which one is easier DTS or SSIS. I have come to know that SSIS is like informatica and no need to right big big stored procedure as we do in DTS for ETL.

The answer is "it depends". if you have an Informatica background then SSIS will definately be easier. This may help:

Conchango Describes How SQL Server 2005 Integration Services Compares with Informatica
http://www.microsoft.com/sql/technologies/integration/conchango.mspx

Ag_dwh wrote:

3.If I make a part of Datawarehouse in DTS and the other in SSIS, will everything work.

You can have your data warehouse in SQL 2000 and your ETL done in SSIS. is that what you mean?

Ag_dwh wrote:

4.If suppose i have shared dimension "X".in the first phase it is populated by DTS and in the 2nd phase can i also polulate by SSIS simultaneously.

Yes.

-Jamie

|||

this from a (relative) newbie to SSIS...

i was hooked on DTS and intimidated at first by SSIS. The initial learning curve is a bit steep but it's not difficult -- and once you get the basic understanding of Connection Managers and the myriad NEW tools available, there's no turning back. And it's very easy to re-direct packages from one environment to another (dev to testing to production).

seth j hersh