Key cannot be null. Parameter name: key

We just upgraded to SS2005. After the upgrade, we can no longer create
subscriptions out of Execution Snapshot.
Try this experiment:
Create a report, with a simple SQL statement like "select * from CustomerDim
where CustomerPk = @.CustomerPk"
Go to Report Parameter, check the "Allow Null" box
Deploy the report
Go to the report on report server, render the report from Execution Snapshot
Now go to Subscription, and try to create a new subscription. The Parameter
CustomerPk will be grayed out, because of the Execution Snapshot
After you clicked OK, the subscription will return the error:
Key cannot be null. Parameter name: key
This error does not occur before the upgrade.
How can we create subscriptions out of Execution Snapshot in SS2005?
Thanks,
John WI've got the same problem. Did you find any solution?
Regards,
/Mattias
"LBJOHN" wrote:
> We just upgraded to SS2005. After the upgrade, we can no longer create
> subscriptions out of Execution Snapshot.
> Try this experiment:
> Create a report, with a simple SQL statement like "select * from CustomerDim
> where CustomerPk = @.CustomerPk"
> Go to Report Parameter, check the "Allow Null" box
> Deploy the report
> Go to the report on report server, render the report from Execution Snapshot
> Now go to Subscription, and try to create a new subscription. The Parameter
> CustomerPk will be grayed out, because of the Execution Snapshot
> After you clicked OK, the subscription will return the error:
> Key cannot be null. Parameter name: key
> This error does not occur before the upgrade.
> How can we create subscriptions out of Execution Snapshot in SS2005?
> Thanks,
> John W

keep dropping snapshot because of Mirroring

Hi Experts,
i have a doubt btw he Mirroring and snapshot, since we cannot
directly touch the mirror DB, then we only can use snapshot for client
to query, however for my understanding, only way to maintain to the
latest info to client is drop the snapshot DB and create another DB
for snapshot. actually that is very hard for us to do the programming
(keep swtiching DB connection). is there other better solution for
this?try to imagine,we need to always pull the latest information from
warehouse give to customer, 1.we need very offen to drop the snapshot,
2. we need to keep swarp the connection to point to DB.
pls give some advise,
thanks
I would agree that a database snapshot on a database mirror is not a good
solution for querying data if you need the data to be current. Mirroring is
primarily a high-availability solution. Using a snapshot of the mirror
makes the secondary available for queries but providing a queryable database
is not the main use for a mirror. If you want to be able to query an up to
date copy of the data, you would be much better off using transactional
replication to maintain the queryable copy. If you need a mirror for
availability purposes and still want to query the mirror you will have to
live with the limitations of database snapshots. This includes having to
reconnect to get to the latest snapshot. I assume that the easiest way to
do this would be to provide a service that tracks and maintains the current
version and hands out connections to application that need them.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"XJ" <ianyian@.gmail.com> wrote in message
news:1180451905.626097.230740@.i13g2000prf.googlegr oups.com...
> Hi Experts,
> i have a doubt btw he Mirroring and snapshot, since we cannot
> directly touch the mirror DB, then we only can use snapshot for client
> to query, however for my understanding, only way to maintain to the
> latest info to client is drop the snapshot DB and create another DB
> for snapshot. actually that is very hard for us to do the programming
> (keep swtiching DB connection). is there other better solution for
> this?try to imagine,we need to always pull the latest information from
> warehouse give to customer, 1.we need very offen to drop the snapshot,
> 2. we need to keep swarp the connection to point to DB.
> pls give some advise,
> thanks
>

keep dropping snapshot because of Mirroring

Hi Experts,
i have a doubt btw he Mirroring and snapshot, since we cannot
directly touch the mirror DB, then we only can use snapshot for client
to query, however for my understanding, only way to maintain to the
latest info to client is drop the snapshot DB and create another DB
for snapshot. actually that is very hard for us to do the programming
(keep swtiching DB connection). is there other better solution for
this?try to imagine,we need to always pull the latest information from
warehouse give to customer, 1.we need very offen to drop the snapshot,
2. we need to keep swarp the connection to point to DB.
pls give some advise,
thanksI would agree that a database snapshot on a database mirror is not a good
solution for querying data if you need the data to be current. Mirroring is
primarily a high-availability solution. Using a snapshot of the mirror
makes the secondary available for queries but providing a queryable database
is not the main use for a mirror. If you want to be able to query an up to
date copy of the data, you would be much better off using transactional
replication to maintain the queryable copy. If you need a mirror for
availability purposes and still want to query the mirror you will have to
live with the limitations of database snapshots. This includes having to
reconnect to get to the latest snapshot. I assume that the easiest way to
do this would be to provide a service that tracks and maintains the current
version and hands out connections to application that need them.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"XJ" <ianyian@.gmail.com> wrote in message
news:1180451905.626097.230740@.i13g2000prf.googlegroups.com...
> Hi Experts,
> i have a doubt btw he Mirroring and snapshot, since we cannot
> directly touch the mirror DB, then we only can use snapshot for client
> to query, however for my understanding, only way to maintain to the
> latest info to client is drop the snapshot DB and create another DB
> for snapshot. actually that is very hard for us to do the programming
> (keep swtiching DB connection). is there other better solution for
> this?try to imagine,we need to always pull the latest information from
> warehouse give to customer, 1.we need very offen to drop the snapshot,
> 2. we need to keep swarp the connection to point to DB.
> pls give some advise,
> thanks
>

keep dropping snapshot because of Mirroring

Hi Experts,
i have a doubt btw he Mirroring and snapshot, since we cannot
directly touch the mirror DB, then we only can use snapshot for client
to query, however for my understanding, only way to maintain to the
latest info to client is drop the snapshot DB and create another DB
for snapshot. actually that is very hard for us to do the programming
(keep swtiching DB connection). is there other better solution for
this?try to imagine,we need to always pull the latest information from
warehouse give to customer, 1.we need very offen to drop the snapshot,
2. we need to keep swarp the connection to point to DB.
pls give some advise,
thanksI would agree that a database snapshot on a database mirror is not a good
solution for querying data if you need the data to be current. Mirroring is
primarily a high-availability solution. Using a snapshot of the mirror
makes the secondary available for queries but providing a queryable database
is not the main use for a mirror. If you want to be able to query an up to
date copy of the data, you would be much better off using transactional
replication to maintain the queryable copy. If you need a mirror for
availability purposes and still want to query the mirror you will have to
live with the limitations of database snapshots. This includes having to
reconnect to get to the latest snapshot. I assume that the easiest way to
do this would be to provide a service that tracks and maintains the current
version and hands out connections to application that need them.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"XJ" <ianyian@.gmail.com> wrote in message
news:1180451905.626097.230740@.i13g2000prf.googlegroups.com...
> Hi Experts,
> i have a doubt btw he Mirroring and snapshot, since we cannot
> directly touch the mirror DB, then we only can use snapshot for client
> to query, however for my understanding, only way to maintain to the
> latest info to client is drop the snapshot DB and create another DB
> for snapshot. actually that is very hard for us to do the programming
> (keep swtiching DB connection). is there other better solution for
> this?try to imagine,we need to always pull the latest information from
> warehouse give to customer, 1.we need very offen to drop the snapshot,
> 2. we need to keep swarp the connection to point to DB.
> pls give some advise,
> thanks
>