SQL Server 2005 Standard Edition.
Using wizard, no problem to use SQL to import from ODBC data source. Saved
the DTS job to an SSIS package, unable to use with agent scheduler.
Error is DTS_E_PRODUCTLEVELTOLOW.
Please help why is this happening?Frank
Do you want to move jobs to SQL Server 2005?
"Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> SQL Server 2005 Standard Edition.
> Using wizard, no problem to use SQL to import from ODBC data source. Saved
> the DTS job to an SSIS package, unable to use with agent scheduler.
> Error is DTS_E_PRODUCTLEVELTOLOW.
> Please help why is this happening?|||I just want them to run as scheduled without operator intervention. I don't
really care how it do it.
Does that make sense?
thanks in advance..
"Uri Dimant" wrote:
> Frank
> Do you want to move jobs to SQL Server 2005?
>
> "Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
> message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> > SQL Server 2005 Standard Edition.
> >
> > Using wizard, no problem to use SQL to import from ODBC data source. Saved
> > the DTS job to an SSIS package, unable to use with agent scheduler.
> >
> > Error is DTS_E_PRODUCTLEVELTOLOW.
> >
> > Please help why is this happening?
>
>
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Friday, March 23, 2012
Help with agent job to import from ODBC?
SQL Server 2005 Standard Edition.
Using wizard, no problem to use SQL to import from ODBC data source. Saved
the DTS job to an SSIS package, unable to use with agent scheduler.
Error is DTS_E_PRODUCTLEVELTOLOW.
Please help why is this happening?
Frank
Do you want to move jobs to SQL Server 2005?
"Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> SQL Server 2005 Standard Edition.
> Using wizard, no problem to use SQL to import from ODBC data source. Saved
> the DTS job to an SSIS package, unable to use with agent scheduler.
> Error is DTS_E_PRODUCTLEVELTOLOW.
> Please help why is this happening?
|||I just want them to run as scheduled without operator intervention. I don't
really care how it do it.
Does that make sense?
thanks in advance..
"Uri Dimant" wrote:
> Frank
> Do you want to move jobs to SQL Server 2005?
>
> "Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
> message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
>
>
Using wizard, no problem to use SQL to import from ODBC data source. Saved
the DTS job to an SSIS package, unable to use with agent scheduler.
Error is DTS_E_PRODUCTLEVELTOLOW.
Please help why is this happening?
Frank
Do you want to move jobs to SQL Server 2005?
"Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
> SQL Server 2005 Standard Edition.
> Using wizard, no problem to use SQL to import from ODBC data source. Saved
> the DTS job to an SSIS package, unable to use with agent scheduler.
> Error is DTS_E_PRODUCTLEVELTOLOW.
> Please help why is this happening?
|||I just want them to run as scheduled without operator intervention. I don't
really care how it do it.
Does that make sense?
thanks in advance..
"Uri Dimant" wrote:
> Frank
> Do you want to move jobs to SQL Server 2005?
>
> "Frank Ricciardi" <FrankRicciardi@.discussions.microsoft.com> wrote in
> message news:0EE47C4D-589D-4B95-81EB-7F1DE5988A2E@.microsoft.com...
>
>
Sunday, February 26, 2012
Help SP3a installation error
I have just installed a new Win2000 server, and loaded
SQL2000 Standard Edition. As soon as I try to install sp3a
I get the following error:
"Setup Initialization error.
Access is denied.
Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
Target: ...path\temp\setupsql.ini"
I am running the installation as administrator.| I have just installed a new Win2000 server, and loaded
| SQL2000 Standard Edition. As soon as I try to install sp3a
| I get the following error:
| "Setup Initialization error.
| Access is denied.
| Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
| Target: ...path\temp\setupsql.ini"
|
| I am running the installation as administrator.
--
Hi Sean,
Check c:\winnt\temp folder and see if setupsql.ini already exists. If it
does,
delete it. This should allow setupsql to complete successfully.
Hope this helps,
--
Eric Cárdenas
SQL Server support
SQL2000 Standard Edition. As soon as I try to install sp3a
I get the following error:
"Setup Initialization error.
Access is denied.
Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
Target: ...path\temp\setupsql.ini"
I am running the installation as administrator.| I have just installed a new Win2000 server, and loaded
| SQL2000 Standard Edition. As soon as I try to install sp3a
| I get the following error:
| "Setup Initialization error.
| Access is denied.
| Source: D:\installs\SP3a-SQL2000\x86\setup\sqlspre.ini
| Target: ...path\temp\setupsql.ini"
|
| I am running the installation as administrator.
--
Hi Sean,
Check c:\winnt\temp folder and see if setupsql.ini already exists. If it
does,
delete it. This should allow setupsql to complete successfully.
Hope this helps,
--
Eric Cárdenas
SQL Server support
Sunday, February 19, 2012
Help Req: how to upgrade from MSDE to Standard Edition
I have Merge Publication with SQL Standard Edition publisher
and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
Can I do this without breaking the subscription (i.e. simple upgrade),
or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
and re-subscribe to publication.
What is the best practice ?
Any advice or link is appreciated.
Pagus
..
The best approach would be to backup the databases, upgrade, restore them,
and then do no sync (the subscriber already has the schema and data)
subscriptions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pagus" <pagus@.writeme.com> wrote in message
news:85dfm05hhog0h9h42v54vu2c81f95nn5pq@.4ax.com...
> I have Merge Publication with SQL Standard Edition publisher
> and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
> to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
> Can I do this without breaking the subscription (i.e. simple upgrade),
> or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
> and re-subscribe to publication.
> What is the best practice ?
> Any advice or link is appreciated.
> Pagus
> .
|||I did it and it works fine.
Thank you Hilary !
On Sat, 9 Oct 2004 22:33:42 -0400, "Hilary Cotter"
<hilary.cotter@.gmail.com> wrote:
>The best approach would be to backup the databases, upgrade, restore them,
>and then do no sync (the subscriber already has the schema and data)
>subscriptions.
and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
Can I do this without breaking the subscription (i.e. simple upgrade),
or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
and re-subscribe to publication.
What is the best practice ?
Any advice or link is appreciated.
Pagus
..
The best approach would be to backup the databases, upgrade, restore them,
and then do no sync (the subscriber already has the schema and data)
subscriptions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pagus" <pagus@.writeme.com> wrote in message
news:85dfm05hhog0h9h42v54vu2c81f95nn5pq@.4ax.com...
> I have Merge Publication with SQL Standard Edition publisher
> and MSDE subscribers. Due to database size (1,8 GB) I'm preparing
> to upgrade SQL Server subscribers from MSDE SP3a to Standard Edition.
> Can I do this without breaking the subscription (i.e. simple upgrade),
> or I have to unsubscribe , upgrade to SQL Standard Edition SP3a
> and re-subscribe to publication.
> What is the best practice ?
> Any advice or link is appreciated.
> Pagus
> .
|||I did it and it works fine.
Thank you Hilary !
On Sat, 9 Oct 2004 22:33:42 -0400, "Hilary Cotter"
<hilary.cotter@.gmail.com> wrote:
>The best approach would be to backup the databases, upgrade, restore them,
>and then do no sync (the subscriber already has the schema and data)
>subscriptions.
Labels:
database,
due,
edition,
merge,
microsoft,
msde,
mysql,
oracle,
preparingto,
publication,
publisherand,
req,
server,
size,
sql,
standard,
subscribers,
upgrade
Subscribe to:
Posts (Atom)