New Data-driven Subscription 'Button'

Hi,
I am trying to set up a data-driven subscription. But the button is not
visible on the subscriptions tab. I have also made sure that
1) the report uses stored credentials.
2) A report that includes parameters.
3) The report server that is configured to use the e-mail delivery
extension.
4) SQL Agent service is running.
5) SQL Server database that contains subscriber information.
Can anybody help?
Snippet from books online:
To open this page, select a report, click the Subscriptions tab at the top
of the page, and then click New Data-driven Subscription. The report must
use stored credentials in order for this button to be enabled.
From this I was expecting to see a button nomatter what.Please read this related newsgroup thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=ba9997ba-d3c3-4ac5-bf9f-6881244ba961&sloc=en-us
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Phil Koay" <phil.koay@.hydro.com.au> wrote in message
news:%23ijs7P1AFHA.2112@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I am trying to set up a data-driven subscription. But the button is not
> visible on the subscriptions tab. I have also made sure that
> 1) the report uses stored credentials.
> 2) A report that includes parameters.
> 3) The report server that is configured to use the e-mail delivery
> extension.
> 4) SQL Agent service is running.
> 5) SQL Server database that contains subscriber information.
> Can anybody help?
> Snippet from books online:
> To open this page, select a report, click the Subscriptions tab at the top
> of the page, and then click New Data-driven Subscription. The report must
> use stored credentials in order for this button to be enabled.
> From this I was expecting to see a button nomatter what.
>|||Thanks for such a prompt and accurate response!
I am indeed using the standard edition of Reporting services and that is why
there is no option of "data driven subscriptions"
I have the following scenario:
I work in a company that has a number of SQL Enterprise licences. However I
would be unable to install Report service on any of these machines, or have
the report services database stored on these machine. Do you know if I can
legally:
1. Install Reporting Services Enterprise edition on seperate box (which has
MS SQL Server standard edition installed on it)
2. Use the local 'MS SQL Server standard edition' as the database for the
'Reporting Services Enterprise'
(from the books online is seems that this is ok to do technically see
'Edition compatibility', but is it legal, and will it have all the same
functionality as if stored on a SQL enterprise?)
Thanks!
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:eCrCHX1AFHA.3120@.TK2MSFTNGP12.phx.gbl...
> Please read this related newsgroup thread:
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlser
ver.reportingsvcs&mid=ba9997ba-d3c3-4ac5-bf9f-6881244ba961&sloc=en-us
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Phil Koay" <phil.koay@.hydro.com.au> wrote in message
> news:%23ijs7P1AFHA.2112@.TK2MSFTNGP09.phx.gbl...
> > Hi,
> >
> > I am trying to set up a data-driven subscription. But the button is not
> > visible on the subscriptions tab. I have also made sure that
> >
> > 1) the report uses stored credentials.
> >
> > 2) A report that includes parameters.
> >
> > 3) The report server that is configured to use the e-mail delivery
> > extension.
> >
> > 4) SQL Agent service is running.
> >
> > 5) SQL Server database that contains subscriber information.
> > Can anybody help?
> >
> > Snippet from books online:
> >
> > To open this page, select a report, click the Subscriptions tab at the
top
> > of the page, and then click New Data-driven Subscription. The report
must
> > use stored credentials in order for this button to be enabled.
> >
> > From this I was expecting to see a button nomatter what.
> >
> >
>|||Note that if you are installing Enterprise you need an enterprise license
for that box. Having Enterprise SQL Servers somewhere else doesn't help. You
can use a remote DB as the object store (RS uses SQL Server to store lots of
things and has to have one around), i.e. RS can be on a different box than
the SQL Server used but as soon as you do that you have to purchase a
license.
I don't know if you can install Enterprise RS using Standard as the object
store. I never tried that. Just wanted to make sure you understand the
licensing.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Phil Koay" <phil.koay@.hydro.com.au> wrote in message
news:%23KGYe%232AFHA.824@.TK2MSFTNGP11.phx.gbl...
> Thanks for such a prompt and accurate response!
> I am indeed using the standard edition of Reporting services and that is
why
> there is no option of "data driven subscriptions"
> I have the following scenario:
> I work in a company that has a number of SQL Enterprise licences. However
I
> would be unable to install Report service on any of these machines, or
have
> the report services database stored on these machine. Do you know if I can
> legally:
> 1. Install Reporting Services Enterprise edition on seperate box (which
has
> MS SQL Server standard edition installed on it)
> 2. Use the local 'MS SQL Server standard edition' as the database for the
> 'Reporting Services Enterprise'
> (from the books online is seems that this is ok to do technically see
> 'Edition compatibility', but is it legal, and will it have all the same
> functionality as if stored on a SQL enterprise?)
> Thanks!
>
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:eCrCHX1AFHA.3120@.TK2MSFTNGP12.phx.gbl...
> > Please read this related newsgroup thread:
> >
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlser
> ver.reportingsvcs&mid=ba9997ba-d3c3-4ac5-bf9f-6881244ba961&sloc=en-us
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Phil Koay" <phil.koay@.hydro.com.au> wrote in message
> > news:%23ijs7P1AFHA.2112@.TK2MSFTNGP09.phx.gbl...
> > > Hi,
> > >
> > > I am trying to set up a data-driven subscription. But the button is
not
> > > visible on the subscriptions tab. I have also made sure that
> > >
> > > 1) the report uses stored credentials.
> > >
> > > 2) A report that includes parameters.
> > >
> > > 3) The report server that is configured to use the e-mail delivery
> > > extension.
> > >
> > > 4) SQL Agent service is running.
> > >
> > > 5) SQL Server database that contains subscriber information.
> > > Can anybody help?
> > >
> > > Snippet from books online:
> > >
> > > To open this page, select a report, click the Subscriptions tab at the
> top
> > > of the page, and then click New Data-driven Subscription. The report
> must
> > > use stored credentials in order for this button to be enabled.
> > >
> > > From this I was expecting to see a button nomatter what.
> > >
> > >
> >
> >
>

New Database Name not visible while DSN setup

Hi,
I have taken backup(connectdb.bak) from production and
created the database in test server. For that I used
following procedure,
In sql query analyzer, I executed the following two steps
consecutively.
1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak'
2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak' WITH
MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
This created a new database "newdb" in test server from
the back up file connectdb.bak.
I want to connect to this database.
Now while going through SQL server DSN configuration,
there comes an option where we get the following option,
"change the default database to"
While clicking in this box,we get a drop down listing of
all the databases. Here I am stuck. Ideally the "newdb"
database which I have created from connectdb.bak file,
should be visible here so that I can choose to connect to
it. But it's not visible here and unless it's visible here
I can't do anything. The otherdatabases which were present
in the test server since beginning are visible accept this
one.
Please help. It's urgent
regards,
Vishal
Check to see if the login/user for whom you are setting up
the DSN is a user in the database that has been restored. It
sounds like they users could have been orphaned.
You can find a good article on orphaned users and
troubleshooting techniques, links to KB articles at:
http://vyaskn.tripod.com/troubleshoo...phan_users.htm
-Sue
On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I have taken backup(connectdb.bak) from production and
>created the database in test server. For that I used
>following procedure,
>In sql query analyzer, I executed the following two steps
>consecutively.
>1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak'
>2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak' WITH
>MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
>MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
>This created a new database "newdb" in test server from
>the back up file connectdb.bak.
>I want to connect to this database.
>Now while going through SQL server DSN configuration,
>there comes an option where we get the following option,
>"change the default database to"
>While clicking in this box,we get a drop down listing of
>all the databases. Here I am stuck. Ideally the "newdb"
>database which I have created from connectdb.bak file,
>should be visible here so that I can choose to connect to
>it. But it's not visible here and unless it's visible here
>I can't do anything. The otherdatabases which were present
>in the test server since beginning are visible accept this
>one.
>Please help. It's urgent
>regards,
>Vishal
>
|||If this is a new serer then the user exists in the
database but not in master. You first need to create the
login. Then synch up the users with sp_change_users_login
>--Original Message--
>Check to see if the login/user for whom you are setting up
>the DSN is a user in the database that has been restored.
It
>sounds like they users could have been orphaned.
>You can find a good article on orphaned users and
>troubleshooting techniques, links to KB articles at:
>http://vyaskn.tripod.com/troubleshoo...phan_users.htm
>-Sue
>On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
><anonymous@.discussions.microsoft.com> wrote:
steps
to
here
present
this
>.
>

New Database Name not visible while DSN setup

Hi,
I have taken backup(connectdb.bak) from production and
created the database in test server. For that I used
following procedure,
In sql query analyzer, I executed the following two steps
consecutively.
1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak'
2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
\Backup\connectdb.bak' WITH
MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
This created a new database "newdb" in test server from
the back up file connectdb.bak.
I want to connect to this database.
Now while going through SQL server DSN configuration,
there comes an option where we get the following option,
"change the default database to"
While clicking in this box,we get a drop down listing of
all the databases. Here I am stuck. Ideally the "newdb"
database which I have created from connectdb.bak file,
should be visible here so that I can choose to connect to
it. But it's not visible here and unless it's visible here
I can't do anything. The otherdatabases which were present
in the test server since beginning are visible accept this
one.
Please help. It's urgent
regards,
VishalCheck to see if the login/user for whom you are setting up
the DSN is a user in the database that has been restored. It
sounds like they users could have been orphaned.
You can find a good article on orphaned users and
troubleshooting techniques, links to KB articles at:
http://vyaskn.tripod.com/troublesho...rphan_users.htm
-Sue
On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>I have taken backup(connectdb.bak) from production and
>created the database in test server. For that I used
>following procedure,
>In sql query analyzer, I executed the following two steps
>consecutively.
>1. RESTORE FILELISTONLY FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak'
>2. RESTORE DATABASE newdb FROM DISK = 'c:\Mssql7
>\Backup\connectdb.bak' WITH
>MOVE 'connectdb_Data' TO 'c:\test\newdb.mdf',
>MOVE 'connectdb_log' TO 'c:\test\newdb_log.ldf'
>This created a new database "newdb" in test server from
>the back up file connectdb.bak.
>I want to connect to this database.
>Now while going through SQL server DSN configuration,
>there comes an option where we get the following option,
>"change the default database to"
>While clicking in this box,we get a drop down listing of
>all the databases. Here I am stuck. Ideally the "newdb"
>database which I have created from connectdb.bak file,
>should be visible here so that I can choose to connect to
>it. But it's not visible here and unless it's visible here
>I can't do anything. The otherdatabases which were present
>in the test server since beginning are visible accept this
>one.
>Please help. It's urgent
>regards,
>Vishal
>|||If this is a new serer then the user exists in the
database but not in master. You first need to create the
login. Then synch up the users with sp_change_users_login
>--Original Message--
>Check to see if the login/user for whom you are setting up
>the DSN is a user in the database that has been restored.
It
>sounds like they users could have been orphaned.
>You can find a good article on orphaned users and
>troubleshooting techniques, links to KB articles at:
>http://vyaskn.tripod.com/troublesho...rphan_users.htm
>-Sue
>On Thu, 1 Apr 2004 08:40:14 -0800, "vishal kumar"
><anonymous@.discussions.microsoft.com> wrote:
>
steps
to
here
present
this
>.
>