Hi !
We are on SQL SERVER 2000 SP3.
We recently had a problem where it appeared (after an extensive reseach via
DBCC checkdb)
we had duplicate identical rows enter a table that had a unique clustered
index defined on most
columns in the table. DBCC checkdb kept reporting corrupt index pages .
After running a number of DBCC checkdb and DBCC reindex the database was
flagged
as (Suspect). We correted the (Suspect) problem by re-loading a copy of an
already corrupt database and deleting duplicate rows (set rowcount 1; DELETE
..).
After that exersise, DBCC checkdb showed no more problems.
One thing to note, prior to 2000, the create index syntax allowed for the
following options:
IGNORE_DUP_ROW and ALLOW_DUP_ROW.
In 2000, those options were dropped from the syntax ... I wonder if this
created a hole ...
The question is: Why did the database allowe duplicate rows to enter into a
table with
a UNIQUE CLUSTERED INDEX defined '
Can anyone offer any help ' Many thanks !
Here is the table:
CREATE TABLE dbo.CROSS_REF_DATA_IDENTIFIERS (
ASSET_ID bigint NOT NULL ,
ID_CD varchar (3) AS NOT NULL ,
ID_NUMBER varchar (30) AS NOT NULL ,
ID_EFFECTIVE_DATE datetime NOT NULL ,
PROCESSED int NULL ,
CONSTRAINT CROSS_REF_DATA_IDENTIFIERS_PK PRIMARY KEY CLUSTERED
(ASSET_ID,
ID_CD,
ID_NUMBER,
ID_EFFECTIVE_DATE
) ON PRIMARY ,
CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_X_CORE_INF
ORMATION FOREIGN KEY
(ASSET_ID) REFERENCES dbo.X_CORE_INFORMATION (ASSET_ID),
CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_CDS_VENDOR
_SRC FOREIGN KEY
(ID_CD) REFERENCES dbo.CDS_VENDOR_SRC ( CODE)
) ON PRIMARYHi,Dean
Ok, what is about sample data?
"Dean Nates" <dnatenzon@.alexandra.net> wrote in message
news:uAYMKNrBEHA.2888@.TK2MSFTNGP09.phx.gbl...
> Hi !
> We are on SQL SERVER 2000 SP3.
> We recently had a problem where it appeared (after an extensive reseach
via
> DBCC checkdb)
> we had duplicate identical rows enter a table that had a unique clustered
> index defined on most
> columns in the table. DBCC checkdb kept reporting corrupt index pages .
> After running a number of DBCC checkdb and DBCC reindex the database was
> flagged
> as (Suspect). We correted the (Suspect) problem by re-loading a copy of an
> already corrupt database and deleting duplicate rows (set rowcount 1;
DELETE
> ..).
> After that exersise, DBCC checkdb showed no more problems.
> One thing to note, prior to 2000, the create index syntax allowed for the
> following options:
> IGNORE_DUP_ROW and ALLOW_DUP_ROW.
> In 2000, those options were dropped from the syntax ... I wonder if this
> created a hole ...
> The question is: Why did the database allowe duplicate rows to enter into
a
> table with
> a UNIQUE CLUSTERED INDEX defined '
> Can anyone offer any help ' Many thanks !
> Here is the table:
> CREATE TABLE dbo.CROSS_REF_DATA_IDENTIFIERS (
> ASSET_ID bigint NOT NULL ,
> ID_CD varchar (3) AS NOT NULL ,
> ID_NUMBER varchar (30) AS NOT NULL ,
> ID_EFFECTIVE_DATE datetime NOT NULL ,
> PROCESSED int NULL ,
> CONSTRAINT CROSS_REF_DATA_IDENTIFIERS_PK PRIMARY KEY CLUSTERED
> (ASSET_ID,
> ID_CD,
> ID_NUMBER,
> ID_EFFECTIVE_DATE
> ) ON PRIMARY ,
> CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_X_CORE_INF
ORMATION FOREIGN KEY
> (ASSET_ID) REFERENCES dbo.X_CORE_INFORMATION (ASSET_ID),
> CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_CDS_VENDOR
_SRC FOREIGN KEY
> (ID_CD) REFERENCES dbo.CDS_VENDOR_SRC ( CODE)
> ) ON PRIMARY
>
>|||Here is the actual sample of what DBCC checkdb reported:
Error: 8908, Severity: 22, State: 6
Table error: Database ID 6, object ID 1065770854, index ID 0. Chain linkage
mismatch. (1:574284)->next = (1:574285), but (1:574285)->prev = (1:481988 )
.
"Dean Nates" <dnatenzon@.alexandra.net> wrote in message
news:uAYMKNrBEHA.2888@.TK2MSFTNGP09.phx.gbl...
> Hi !
> We are on SQL SERVER 2000 SP3.
> We recently had a problem where it appeared (after an extensive reseach
via
> DBCC checkdb)
> we had duplicate identical rows enter a table that had a unique clustered
> index defined on most
> columns in the table. DBCC checkdb kept reporting corrupt index pages .
> After running a number of DBCC checkdb and DBCC reindex the database was
> flagged
> as (Suspect). We correted the (Suspect) problem by re-loading a copy of an
> already corrupt database and deleting duplicate rows (set rowcount 1;
DELETE
> ..).
> After that exersise, DBCC checkdb showed no more problems.
> One thing to note, prior to 2000, the create index syntax allowed for the
> following options:
> IGNORE_DUP_ROW and ALLOW_DUP_ROW.
> In 2000, those options were dropped from the syntax ... I wonder if this
> created a hole ...
> The question is: Why did the database allowe duplicate rows to enter into
a
> table with
> a UNIQUE CLUSTERED INDEX defined '
> Can anyone offer any help ' Many thanks !
> Here is the table:
> CREATE TABLE dbo.CROSS_REF_DATA_IDENTIFIERS (
> ASSET_ID bigint NOT NULL ,
> ID_CD varchar (3) AS NOT NULL ,
> ID_NUMBER varchar (30) AS NOT NULL ,
> ID_EFFECTIVE_DATE datetime NOT NULL ,
> PROCESSED int NULL ,
> CONSTRAINT CROSS_REF_DATA_IDENTIFIERS_PK PRIMARY KEY CLUSTERED
> (ASSET_ID,
> ID_CD,
> ID_NUMBER,
> ID_EFFECTIVE_DATE
> ) ON PRIMARY ,
> CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_X_CORE_INF
ORMATION FOREIGN KEY
> (ASSET_ID) REFERENCES dbo.X_CORE_INFORMATION (ASSET_ID),
> CONSTRAINT FK_CROSS_REF_DATA_IDENTIFIERS_CDS_VENDOR
_SRC FOREIGN KEY
> (ID_CD) REFERENCES dbo.CDS_VENDOR_SRC ( CODE)
> ) ON PRIMARY
>
>sql
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Monday, March 26, 2012
Friday, March 9, 2012
dual processor benefit
Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?
Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>
|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?
Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>
|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
dual processor benefit
Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we shoul
d
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to veri
fy
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we shoul
d
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to veri
fy
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
dual processor benefit
Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>
Friday, February 17, 2012
dts vs. job
I have a DTS package that runs fine on a SQL 7 sp3 box. When I try and run
it as a job it fails with this error:
DTSRun: Loading...
Error: -2147287038 (80030002); Provider Error: 0 (0)
Error string: The system cannot find the file specified.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 713
Any ideas?Check out the following article:
269074 INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
Rand
This posting is provided "as is" with no warranties and confers no rights.|||jj,
The problem is probably the context that DTS is executing under. One thing
to remember is that DTS is a client process, not a server process.
When run interactively, where is it running? If you are running it from your
machine, then access to the package would be obtained using your domain
rights. If you login to the SQL7 box, then the login that you use must have
the proper domain rights to get to the file.
Now, when you run it as a SQL Agent job, it will run either as the SQL
Server service account (e.g. MyDomain/MySQLServer) or if the job is not
owned by a sysadmin it runs as the SQL Agent proxy account (e.g.
MyDomain/MySQLAgentProxy). See:
xp_sql_agent_proxy
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
xp_aa-sz_8sdm.asp
SQL Server Agent Permissions Checks
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_automate_054p.asp
Which ever account is _actually_ in use must have the necessary rights to
access the package.
Russell Fields
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:eLsAD$eBEHA.744@.TK2MSFTNGP10.phx.gbl...
> I have a DTS package that runs fine on a SQL 7 sp3 box. When I try and run
> it as a job it fails with this error:
> DTSRun: Loading...
> Error: -2147287038 (80030002); Provider Error: 0 (0)
> Error string: The system cannot find the file specified.
> Error source: Microsoft Data Transformation Services (DTS) Package
> Help file: sqldts.hlp
> Help context: 713
> Any ideas?
>
it as a job it fails with this error:
DTSRun: Loading...
Error: -2147287038 (80030002); Provider Error: 0 (0)
Error string: The system cannot find the file specified.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 713
Any ideas?Check out the following article:
269074 INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
Rand
This posting is provided "as is" with no warranties and confers no rights.|||jj,
The problem is probably the context that DTS is executing under. One thing
to remember is that DTS is a client process, not a server process.
When run interactively, where is it running? If you are running it from your
machine, then access to the package would be obtained using your domain
rights. If you login to the SQL7 box, then the login that you use must have
the proper domain rights to get to the file.
Now, when you run it as a SQL Agent job, it will run either as the SQL
Server service account (e.g. MyDomain/MySQLServer) or if the job is not
owned by a sysadmin it runs as the SQL Agent proxy account (e.g.
MyDomain/MySQLAgentProxy). See:
xp_sql_agent_proxy
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
xp_aa-sz_8sdm.asp
SQL Server Agent Permissions Checks
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_automate_054p.asp
Which ever account is _actually_ in use must have the necessary rights to
access the package.
Russell Fields
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:eLsAD$eBEHA.744@.TK2MSFTNGP10.phx.gbl...
> I have a DTS package that runs fine on a SQL 7 sp3 box. When I try and run
> it as a job it fails with this error:
> DTSRun: Loading...
> Error: -2147287038 (80030002); Provider Error: 0 (0)
> Error string: The system cannot find the file specified.
> Error source: Microsoft Data Transformation Services (DTS) Package
> Help file: sqldts.hlp
> Help context: 713
> Any ideas?
>
Subscribe to:
Posts (Atom)