Data Driven Subscriptions unavailable, please help

I'm running sql2000 Standard with SP4 applied. I also have Reporting Services 2000 with service packs running on the same machine. I'm trying to get a data-driven subscription, but the button to access is unavailable.

I've assigned the account I'm working under the Publisher role and have modified this role to have all permissions (including managing subscriptions). I have stored credentials with my data source as well.

I can create a standard subscription with no problems, but just don't get the button to do the data-driven option.

Any assistance is appreciated.

You are running RS 2000 Standard Edition. Data driven subscriptions are only available on Enterprise Edition and Developer Edition.

The same applies to data driven subscriptions on RS 2005: http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx

-- Robert

|||Is it possible to run the enterprise edition of Reporting Services on the Standard edition of SQL 2000?|||

Actually, you can run a Reporting Services Enterprise Edition with its metadata store on a SQL Server Standard Edition.

-- Robert

|||We have the same issue and we are using the enterprise version. The user who is trying to set-up the data-driven subscription is also an admin on the report server settings...|||

Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?

|||Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?

Data Driven Subscriptions unavailable, please help

I'm running sql2000 Standard with SP4 applied. I also have Reporting Services 2000 with service packs running on the same machine. I'm trying to get a data-driven subscription, but the button to access is unavailable.

I've assigned the account I'm working under the Publisher role and have modified this role to have all permissions (including managing subscriptions). I have stored credentials with my data source as well.

I can create a standard subscription with no problems, but just don't get the button to do the data-driven option.

Any assistance is appreciated.

You are running RS 2000 Standard Edition. Data driven subscriptions are only available on Enterprise Edition and Developer Edition.

The same applies to data driven subscriptions on RS 2005: http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx

-- Robert

|||Is it possible to run the enterprise edition of Reporting Services on the Standard edition of SQL 2000?|||

Actually, you can run a Reporting Services Enterprise Edition with its metadata store on a SQL Server Standard Edition.

-- Robert

|||We have the same issue and we are using the enterprise version. The user who is trying to set-up the data-driven subscription is also an admin on the report server settings...|||

Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?

|||Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?sql

Data Driven Subscriptions unavailable, please help

I'm running sql2000 Standard with SP4 applied. I also have Reporting Services 2000 with service packs running on the same machine. I'm trying to get a data-driven subscription, but the button to access is unavailable.

I've assigned the account I'm working under the Publisher role and have modified this role to have all permissions (including managing subscriptions). I have stored credentials with my data source as well.

I can create a standard subscription with no problems, but just don't get the button to do the data-driven option.

Any assistance is appreciated.

You are running RS 2000 Standard Edition. Data driven subscriptions are only available on Enterprise Edition and Developer Edition.

The same applies to data driven subscriptions on RS 2005: http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx

-- Robert

|||Is it possible to run the enterprise edition of Reporting Services on the Standard edition of SQL 2000?|||

Actually, you can run a Reporting Services Enterprise Edition with its metadata store on a SQL Server Standard Edition.

-- Robert

|||We have the same issue and we are using the enterprise version. The user who is trying to set-up the data-driven subscription is also an admin on the report server settings...|||

Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?

|||Does anybody know the license implications if you install reporting services 2000 enterprise on a sql server 2000 standard install?

Data Driven Subscriptions

I read somewhere that Data Driven Subscriptions are only for Enterpise Edition.
In this case, why is it available in the Standard edition web interface of
the Report Manager?Data driven subscriptions are not available with Standard edition
(http://www.microsoft.com/sql/reporting/productinfo/features.asp). The
button is probably there because the subscription types are not
configurable.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"Minas Papageorgiou" <MinasPapageorgiou@.discussions.microsoft.com> wrote in
message news:5C3CF96E-15DC-45F0-9C81-E4B913FDAECB@.microsoft.com...
> I read somewhere that Data Driven Subscriptions are only for Enterpise
Edition.
> In this case, why is it available in the Standard edition web interface of
> the Report Manager?sql

Data Conversion supported on Standard Edition?

I created an Integration Services Package that runs fine from my local computer using BIDS. However when I imported into our SQL Server and try to run it from there I get the following error:

DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Data Conversion"

We are running SQL Server 2005 Standard Edition 64-bit.

We have integration services installed on the server. Is data conversion something that is not supported on Standard Edition?

Also have a similar message for "Send Mail Task."

Is there anywhere that outlines what features are supported on each version?

What version of SQL Server are you running on your developer's workstation?|||

I'm running BIDS on my workstation which is connecting to our SQL Server. The same SQL Server where the integration package will not run from when imported into. So I'm actually not running a full blown SQL Server database on my workstation, just using BIDS on it along with Studio.

The Management Studio on my workstation is 9.00.3042.

SQL Server Integration Services is 9.00.3042. (Found by going to About > Help in Visual Studio)

Our SQL Server version is 9.00.3050

|||So both your workstation and the server are running SQL Server Standard edition? Not developer/enterprise edition?|||

Server is definitely Standard Edition. When I installed the workstation components on my workstation I honestly don't remember if I installed them from the Standard edition or Developer edition. Most likely I installed the workstation components using the Developer edition. Is there a way to check?

I guess that would explain why it works on my workstation but not on the server?

|||

Erikk Ross wrote:

Server is definitely Standard Edition. When I installed the workstation components on my workstation I honestly don't remember if I installed them from the Standard edition or Developer edition. Most likely I installed the workstation components using the Developer edition. Is there a way to check?

Run this query on the server and again on your local version:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')|||

Yeah, like I said I don't have the actual Database engine installed on my workstation. But our server version is SP2: 9.00.3050.

So I guess Data Conversion is not supported in Standard Edition? Or send mail? Is there a matrix somewhere that shows what features in Integration Services are supported in each version of SQL Server? It would seem to me that data conversion is something that is pretty common...I'm a little suprised it would require the Enterprise edition.

|||Alright, well, I do think it's because you're developing a package in a Developer environment, which is a higher level than the Standard edition that your server runs. If your server was an Enterprise version, you wouldn't have a problem (of course).

Uninstall and reinstall the SSIS components from the Standard Edition CDs and you should be fine. The Data Conversion component should work in the Standard Edition.|||

Phil Brammer wrote:

Alright, well, I do think it's because you're developing a package in a Developer environment, which is a higher level than the Standard edition that your server runs. If your server was an Enterprise version, you wouldn't have a problem (of course).

Uninstall and reinstall the SSIS components from the Standard Edition CDs and you should be fine. The Data Conversion component should work in the Standard Edition.

That was indeed the solution. I just did a quick test and creating the package from a Standard edition version did allow the data conversion to work correctly. Thank you!!

|||

Well, after uninstalling SQL Server workstation components on my development machine and reinstalling the Standard version it did not fix my problem. Any package created on my local development machine still does not work when imported into SQL Server. Get the same Product level to low error.

At least the good news is that I can create packages on the SQL Server itself and they seem to work fine. My best guess is that uninstalling the developer edition and reinstalling the standard edition just wasn't enough. I would suspect that if I was to completely wipe my machine clean then install Standard Edition it would probably be ok. But that is more hassle than it's worth.

|||

Erikk Ross wrote:

Well, after uninstalling SQL Server workstation components on my development machine and reinstalling the Standard version it did not fix my problem. Any package created on my local development machine still does not work when imported into SQL Server. Get the same Product level to low error.

At least the good news is that I can create packages on the SQL Server itself and they seem to work fine. My best guess is that uninstalling the developer edition and reinstalling the standard edition just wasn't enough. I would suspect that if I was to completely wipe my machine clean then install Standard Edition it would probably be ok. But that is more hassle than it's worth.

Any NEW packages created still don't work?|||

Correct, I created a brand new package. Well I first tried to rebuild my old package but that didn't work either, so I just created a new one. Same problems, runs fine on my local workstation, but when imported into SQL Server gives the same error.

I am currently installing standard edition workstation components on a new workstation with Visual Studio and will try to create a package from there and import it and see if that works.

|||Run this on the server, please:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')|||

Phil Brammer wrote:

Run this on the server, please:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

9.00.3050.00 SP2 Standard Edition (64-bit)

Well now I am completely lost. I just installed the standard edition workstation components on a brand new machine. A machine that has never had SQL Server installed on it. I created a new package in Visual Studio, imported it into our SQL Server, ran it, and still get the same ProductLevelToLow errors.

Error: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Data Conversion".

|||

After reading this I realized my problem: http://blogs.msdn.com/michen/archive/2006/08/11/package-exec-location.aspx

I was running the package from my workstation using Management Studio, unaware that the package was actually running on my local workstation and not on the server. Since it was running on my workstation it required Integration Services to be installed which it wasn't, so that is why I got those error messages. As soon as I ran it directly from the server it worked fine.

*sigh* I wish this was more obvious. I thought that by running it in Management Studio it was just automatically running it on the server.

Data Connection problems - Database not found

I resently purchased a Virtual Windows 2003 Standard Server and I installed
SQL 2000 with Service Pack 3 on it to make sure it was up to date. I can ftp
on this server and everthing but when it comes to making a Microsoft ODBC
connection from my local computer to the virtual server I am not able to hook
up with it I recive a server time out is there something someone can be
patience with me and help me with this problem.
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Can u connect using query analyser.?
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23w2amiThEHA.1156@.TK2MSFTNGP10.phx.gbl...
> I resently purchased a Virtual Windows 2003 Standard Server and I
installed
> SQL 2000 with Service Pack 3 on it to make sure it was up to date. I can
ftp
> on this server and everthing but when it comes to making a Microsoft ODBC
> connection from my local computer to the virtual server I am not able to
hook
> up with it I recive a server time out is there something someone can be
> patience with me and help me with this problem.
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||How would I go about doing that .. I have tried to do the ODBC on my computer
setting up a SWL access to the computer and I still can't hit it..
"SKG" wrote:

> Can u connect using query analyser.?
> "SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
> news:%23w2amiThEHA.1156@.TK2MSFTNGP10.phx.gbl...
> installed
> ftp
> hook
> supports Post Alerts, Ratings, and Searching.
>
>
|||Okay when I ran the ODBC on the local server I found no problems
"Peter" wrote:
[vbcol=seagreen]
> How would I go about doing that .. I have tried to do the ODBC on my computer
> setting up a SWL access to the computer and I still can't hit it..
> "SKG" wrote:

Data Connection problems - Database not found

I resently purchased a Virtual Windows 2003 Standard Server and I installed
SQL 2000 with Service Pack 3 on it to make sure it was up to date. I can ft
p
on this server and everthing but when it comes to making a Microsoft ODBC
connection from my local computer to the virtual server I am not able to hoo
k
up with it I recive a server time out is there something someone can be
patience with me and help me with this problem.
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine sup
ports Post Alerts, Ratings, and Searching.Can u connect using query analyser.?
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23w2amiThEHA.1156@.TK2MSFTNGP10.phx.gbl...
> I resently purchased a Virtual Windows 2003 Standard Server and I
installed
> SQL 2000 with Service Pack 3 on it to make sure it was up to date. I can
ftp
> on this server and everthing but when it comes to making a Microsoft ODBC
> connection from my local computer to the virtual server I am not able to
hook
> up with it I recive a server time out is there something someone can be
> patience with me and help me with this problem.
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.|||How would I go about doing that .. I have tried to do the ODBC on my compute
r
setting up a SWL access to the computer and I still can't hit it..
"SKG" wrote:

> Can u connect using query analyser.?
> "SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
> news:%23w2amiThEHA.1156@.TK2MSFTNGP10.phx.gbl...
> installed
> ftp
> hook
> supports Post Alerts, Ratings, and Searching.
>
>|||Okay when I ran the ODBC on the local server I found no problems
"Peter" wrote:
[vbcol=seagreen]
> How would I go about doing that .. I have tried to do the ODBC on my compu
ter
> setting up a SWL access to the computer and I still can't hit it..
> "SKG" wrote:
>

Daily Backups SQL 2005 Standard Edition

With SQL 2000 I was backing up to a NAS server by mapping a drive share to
Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
focused on a networking issue?
Thanks!
ChrisBackups are always done with the privileges of the account SQL Server is
running under. Does this account have access to that share? You never want
to use mapped drives. Use UNC pathing instead.
Andrew J. Kelly SQL MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:eRk0J22LGHA.420@.tk2msftngp13.phx.gbl...
> With SQL 2000 I was backing up to a NAS server by mapping a drive share to
> Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
> focused on a networking issue?
> Thanks!
> Chris
>

Daily Backups SQL 2005 Standard Edition

With SQL 2000 I was backing up to a NAS server by mapping a drive share to
Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
focused on a networking issue?
Thanks!
Chris
Backups are always done with the privileges of the account SQL Server is
running under. Does this account have access to that share? You never want
to use mapped drives. Use UNC pathing instead.
Andrew J. Kelly SQL MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:eRk0J22LGHA.420@.tk2msftngp13.phx.gbl...
> With SQL 2000 I was backing up to a NAS server by mapping a drive share to
> Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
> focused on a networking issue?
> Thanks!
> Chris
>

Daily Backups SQL 2005 Standard Edition

With SQL 2000 I was backing up to a NAS server by mapping a drive share to
Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
focused on a networking issue?
Thanks!
ChrisBackups are always done with the privileges of the account SQL Server is
running under. Does this account have access to that share? You never want
to use mapped drives. Use UNC pathing instead.
--
Andrew J. Kelly SQL MVP
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:eRk0J22LGHA.420@.tk2msftngp13.phx.gbl...
> With SQL 2000 I was backing up to a NAS server by mapping a drive share to
> Z. Is there a reason that I cannot do this in SQL 2005 now or should I be
> focused on a networking issue?
> Thanks!
> Chris
>