Change image properties at runtime

Hi,
I'm using Reporting Services for SQL2K. My report will need to dynamically
call a custom assembly for each row in a dataset, and then show the image
file that the custom assembly creates. I was thinking of using an Image
control in the report and then changing the path to the image file at
runtime. But I can not figure out how to access the image1.Value property.
Any tips on this or perhaps an alternative solution?
TIA
JonasI found the answer, and it was very easy ;-)
When the control is selected in the Report Designer, it it possible to edit
the properties as usual. The property for Value can also use an Expression,
and voila, this can point to a variable which contains a dynamically created
path.
Brgds
Jonas
"Jonas" <Jonas@.nospam.pl> wrote in message
news:%23z53z3cHGHA.240@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I'm using Reporting Services for SQL2K. My report will need to dynamically
> call a custom assembly for each row in a dataset, and then show the image
> file that the custom assembly creates. I was thinking of using an Image
> control in the report and then changing the path to the image file at
> runtime. But I can not figure out how to access the image1.Value property.
> Any tips on this or perhaps an alternative solution?
> TIA
> Jonas
>
>

Change Domains

I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
cluster in the new Domain, and (b) migrating MSCS to the new domain per
kb26196: "How to Move a Windows Cluster Server from one domain to another",
and then using SQL Server's Setup program, Cluster Administrator, and
regedt32 to migrate the instances to the new domain, per per kb319016: "How
To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?
I had to do this recently. I start from scratch and then attached the
databases. Worked great.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Harvey Hall" <Harvey Hall@.discussions.microsoft.com> wrote in message
news:F21C09DF-36F2-4AF4-B50A-B71D9ACDDBDF@.microsoft.com...
>I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
> considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
> cluster in the new Domain, and (b) migrating MSCS to the new domain per
> kb26196: "How to Move a Windows Cluster Server from one domain to
> another",
> and then using SQL Server's Setup program, Cluster Administrator, and
> regedt32 to migrate the instances to the new domain, per per kb319016:
> "How
> To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?
|||Thanks for your response. Glad to hear that "from scratch" works well. Do you
have any thoughts about what I call plan (b) below, that is:
(b) migrating MSCS to the new domain per kb26196: "How to Move a Windows
Cluster Server from one domain to another", and then using SQL Server's Setup
program, Cluster Administrator, and regedt32 to migrate the instances to the
new domain, per kb319016: "How To: Change Domains for a SQL Server 2000
Failover Cluster"
Would you recommend one approach over another?
"Harvey Hall" wrote:
I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
considering two alternatives: (a) a node by node rebuild to a Win2k3/SQL2k
cluster in the new Domain, and (b) migrating MSCS to the new domain per
kb26196: "How to Move a Windows Cluster Server from one domain to another",
and then using SQL Server's Setup program, Cluster Administrator, and
regedt32 to migrate the instances to the new domain, per per kb319016: "How
To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?
|||Hello Harvey,
With regards to the options I would utilise the option of building from
scratch if this option is available to you as this will gurantee you that
setup is clean, whereas with the migration option using the KB artilces you
have specified you can run into issues which can be caused by objects not
being created during the migration, etc; service account issues, etc.
However the KB articles are tested and proven to work but as is with most
cases if you can start from scratch its always better, especially in a
cluster environment where you want to gurantee a clean environment for high
availability and ease of troubleshooting.
Regards,
Shashank Pawar
SQL Server Support Engineer, Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Change Domains
| thread-index: AcTZXDH2uVyKQNVbSwSq4yvHs8qoUw==
| X-WBNR-Posting-Host: 69.89.128.5
| From: "=?Utf-8?B?SGFydmV5IEhhbGw=?="
<HarveyHall@.discussions.microsoft.com>
| References: <F21C09DF-36F2-4AF4-B50A-B71D9ACDDBDF@.microsoft.com>
| Subject: RE: Change Domains
| Date: Fri, 3 Dec 2004 09:19:07 -0800
| Lines: 20
| Message-ID: <011FD8E0-BBF7-4040-B2BD-1A9098C71D6D@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.clustering
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNGXA
03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.clustering:15918
| X-Tomcat-NG: microsoft.public.sqlserver.clustering
|
| Thanks for your response. Glad to hear that "from scratch" works well. Do
you
| have any thoughts about what I call plan (b) below, that is:
|
| (b) migrating MSCS to the new domain per kb26196: "How to Move a Windows
| Cluster Server from one domain to another", and then using SQL Server's
Setup
| program, Cluster Administrator, and regedt32 to migrate the instances to
the
| new domain, per kb319016: "How To: Change Domains for a SQL Server 2000
| Failover Cluster"
|
| Would you recommend one approach over another?
|
| "Harvey Hall" wrote:
|
| I need to move a Win2k/SQL2k 2-node cluster to another Domain. I'm
| considering two alternatives: (a) a node by node rebuild to a
Win2k3/SQL2k
| cluster in the new Domain, and (b) migrating MSCS to the new domain per
| kb26196: "How to Move a Windows Cluster Server from one domain to
another",
| and then using SQL Server's Setup program, Cluster Administrator, and
| regedt32 to migrate the instances to the new domain, per per kb319016:
"How
| To: Change Doamins for a SQL Server 2000 Failover Cluster". Any advice?
|
sql

Caught in a Replication Catch-22, SQLServer2005

I am currently moving from SQL2K to 2005 and am having trouble incorporating
replication in 2005.
First off, I've found myself in a loop where I have two publications that
"don't exist" even though they show up in my Local Publishers list. I can't
delete tables that are articles in those publications because the tables are
being replicated. However, if I try to delete the publication, I get the
message that the publication doesn't exist. So the tables I need to drop are
bound to a publication that doesn't exist.
I've tried looking in the distribution and master databases to find the
missing links but I can't find anything. Without spending a lot of time
going through how I got in this mess, I'd just like to know if there are some
sp's that I can use to purge these publications once and for all.
Thanks in advance.
Roger.
You don't say which type of replication you are using. My experience
is only with merge replication, in this case I would suggest using
sp_removedbreplication in addition to normal sp_dropmergepublication
(or delete from the Gui)
Please see KB324401 for recommendations from MS. http://
support.microsoft.com/kb/324401
Tim Hill
On Feb 9, 3:33 pm, Roger Denison
<RogerDeni...@.discussions.microsoft.com> wrote:
> I am currently moving from SQL2K to 2005 and am having trouble incorporating
> replication in 2005.
> First off, I've found myself in a loop where I have two publications that
> "don't exist" even though they show up in my Local Publishers list. I can't
> delete tables that are articles in those publications because the tables are
> being replicated. However, if I try to delete the publication, I get the
> message that the publication doesn't exist. So the tables I need to drop are
> bound to a publication that doesn't exist.
> I've tried looking in the distribution and master databases to find the
> missing links but I can't find anything. Without spending a lot of time
> going through how I got in this mess, I'd just like to know if there are some
> sp's that I can use to purge these publications once and for all.
> Thanks in advance.
> --
> Roger.
|||I had a similar problem to this. The only way round it was to script
the publications & subscriptions, remove replication and then
re-enable.
On Fri, 9 Feb 2007 07:33:00 -0800, Roger Denison
<RogerDenison@.discussions.microsoft.com> wrote:

>I am currently moving from SQL2K to 2005 and am having trouble incorporating
>replication in 2005.
>First off, I've found myself in a loop where I have two publications that
>"don't exist" even though they show up in my Local Publishers list. I can't
>delete tables that are articles in those publications because the tables are
>being replicated. However, if I try to delete the publication, I get the
>message that the publication doesn't exist. So the tables I need to drop are
>bound to a publication that doesn't exist.
>I've tried looking in the distribution and master databases to find the
>missing links but I can't find anything. Without spending a lot of time
>going through how I got in this mess, I'd just like to know if there are some
>sp's that I can use to purge these publications once and for all.
>Thanks in advance.