report does not show a table

Hi,

We have a report published to two report servers ( same configuration). this report displays data in two side by side tables. on server 1, the left side table does not get displayed where as both the tables show fine on server 2.

What could be the reason for this

Any help greatly appreciated.

Thanks,

Phani

I assume that the reports are pointing to different databases, so is there any data being returned for the table that doesn't show?|||

Hi,

It is the same report deployed on two webservers so they pull from the same database. One report shows both the tables with data and the second one shows only the right side table with data and does not show left hand side table.

Thanks,

Phani

|||

are the two tables using the same datasource?

could it be a time out issue from sql?

Have you looked into the reportserver log files and compared the results from each report server?

sql

Report deploment to multiple servers SQL Reporting 2005

Hi

Another issue I would like your help:

We are writing reports for different clients. We need to deploy the same reports to different clients (thus also different DataSources). What is the best way to handle this? The folder names would probably be the same.

Andre

Sounds like you need a custom installer that will accept the required input (database name, credentials, folder path) and deploy the reports by calling down to the Report Server APIs. Or, you can script the objects and use the rs.exe utility to deploy. You may also find the RSScripter utility useful.sql

Report across multiple db

Can I use BIDS to create a report that will cross other DB's and servers?
For example - I have a customer DB that has social security #'s on Server1
DB-abc and I want to link to another server Server2 DB-efg - and create a
report with data elements from both DB's.yes, create a Linked Server to the second DB Server. After that you have the
possibility to create a view getting the data from both DB's. build the
report on this view and you are done.
hope this helps.
Regards, Rene
"Joe" schrieb:
> Can I use BIDS to create a report that will cross other DB's and servers?
> For example - I have a customer DB that has social security #'s on Server1
> DB-abc and I want to link to another server Server2 DB-efg - and create a
> report with data elements from both DB's.
>
>|||Just a heads up. Be very very careful with linked tables. If you do a
heterogenous join you will be pulling a massive amount of data locally. With
SQL 2000 it would do this sometimes even when the query was all on a single
remote database as I found out when I went against a large table. SQL 2005
is better at this but you will still see issues with heterogenous joins.
Linked tables are easy to use but dangerous.
One suggestion, do not use four part naming. Use openquery instead. Limit
the data as much as possible bringing it into a temp table and then do your
join there.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rene Fehr" <ReneFehr@.discussions.microsoft.com> wrote in message
news:7242A398-BC81-4DB3-A946-0A4DA7567C2E@.microsoft.com...
> yes, create a Linked Server to the second DB Server. After that you have
> the
> possibility to create a view getting the data from both DB's. build the
> report on this view and you are done.
> hope this helps.
> Regards, Rene
> "Joe" schrieb:
>> Can I use BIDS to create a report that will cross other DB's and servers?
>> For example - I have a customer DB that has social security #'s on
>> Server1
>> DB-abc and I want to link to another server Server2 DB-efg - and create a
>> report with data elements from both DB's.
>>

Replication: Change Distributor

Hello,
I need to change the distributor role from one production server to another
new server. I have 15 servers replicating (transactional) to one central
server, which is the distributor too. Of course, I want to change this role
to another new server.
I have been tested some processes in order to do that, many of them were
certains but I want to know the correct process which is supported by MS.
Thank you a lot.
Maria Pia Fernandez
Maria,
you can deduce the supported path from BOL - the section "Strategies for
Backing Up and Restoring Snapshot and Transactional Replication". The whole
process can be made simpler by preventing any access to the system, then
syncing all subscribers, then backing up the databases (master, msdb,
distribution) on the distributor. You can then restore the databases.
Remember that the server name must be identical for this to work.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||To change the distributor you must drop all subscriptions and publications
and then configure the new distributor and all publishers to use this
distributor. Then recreate you publications and subscriptions. Ensure that
the distributor is clustered.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mpia" <repettos@.telviso.com.ar> wrote in message
news:O7ldpJjVHHA.1120@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I need to change the distributor role from one production server to
> another new server. I have 15 servers replicating (transactional) to one
> central server, which is the distributor too. Of course, I want to change
> this role to another new server.
> I have been tested some processes in order to do that, many of them were
> certains but I want to know the correct process which is supported by MS.
> Thank you a lot.
> Maria Pia Fernandez
>
|||Hilary/Paul, thanks for your answers,
I need to maintain the old distributor!!!! I mean I need to change some
production publications in order to use another new distributor. So, this
new distributor will not have the same name.
Besides, I cant stop replicating, I can stop one of them and change its
distributor and so on.
Maria Pia Fernandez
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:u3GTp0mVHHA.2212@.TK2MSFTNGP02.phx.gbl...
> To change the distributor you must drop all subscriptions and publications
> and then configure the new distributor and all publishers to use this
> distributor. Then recreate you publications and subscriptions. Ensure that
> the distributor is clustered.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mpia" <repettos@.telviso.com.ar> wrote in message
> news:O7ldpJjVHHA.1120@.TK2MSFTNGP02.phx.gbl...
>
|||A publisher can only use a single distributor. Multiple publishers can use
the same distributor on a remote distributor, or they can each have their
own distribution database on the same distributor.
But your configuration is not supported.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mpia" <repettos@.telviso.com.ar> wrote in message
news:epy7SOpVHHA.1200@.TK2MSFTNGP04.phx.gbl...
> Hilary/Paul, thanks for your answers,
> I need to maintain the old distributor!!!! I mean I need to change some
> production publications in order to use another new distributor. So, this
> new distributor will not have the same name.
> Besides, I cant stop replicating, I can stop one of them and change its
> distributor and so on.
> Maria Pia Fernandez
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:u3GTp0mVHHA.2212@.TK2MSFTNGP02.phx.gbl...
>
|||I know that. I will try to explain better (sorry for my English!!)
I have 15 publishers using one distributor. I need to change the distributor
for some publications, so I will have two distributors.How can I change el
distributor for ONE publication?
Thanks.
Maria Pia Fernandez
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%237fq$upVHHA.4872@.TK2MSFTNGP03.phx.gbl...
>A publisher can only use a single distributor. Multiple publishers can use
>the same distributor on a remote distributor, or they can each have their
>own distribution database on the same distributor.
> But your configuration is not supported.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mpia" <repettos@.telviso.com.ar> wrote in message
> news:epy7SOpVHHA.1200@.TK2MSFTNGP04.phx.gbl...
>
|||You will have to drop these publications and disable replication on those
machines whose distributor you wish to change. When recreate replication
configure them to use the different distributor/distributiondb.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mpia" <repettos@.telviso.com.ar> wrote in message
news:OUx%23DFuVHHA.1432@.TK2MSFTNGP02.phx.gbl...
>I know that. I will try to explain better (sorry for my English!!)
> I have 15 publishers using one distributor. I need to change the
> distributor for some publications, so I will have two distributors.How can
> I change el distributor for ONE publication?
> Thanks.
> Maria Pia Fernandez
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%237fq$upVHHA.4872@.TK2MSFTNGP03.phx.gbl...
>
|||Yes, I know that method but I want to do that no need to drop publications.
Is this possible? I think it is possible without using enterprise manager.
Thank for your time!!!!
Maria Pia Fernandez
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eNT6lkuVHHA.4720@.TK2MSFTNGP04.phx.gbl...
> You will have to drop these publications and disable replication on those
> machines whose distributor you wish to change. When recreate replication
> configure them to use the different distributor/distributiondb.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "mpia" <repettos@.telviso.com.ar> wrote in message
> news:OUx%23DFuVHHA.1432@.TK2MSFTNGP02.phx.gbl...
>
|||There is no supported way to do this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"mpia" <repettos@.telviso.com.ar> wrote in message
news:%23bwacHvVHHA.4028@.TK2MSFTNGP04.phx.gbl...
> Yes, I know that method but I want to do that no need to drop
> publications.
> Is this possible? I think it is possible without using enterprise manager.
> Thank for your time!!!!
> Maria Pia Fernandez
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eNT6lkuVHHA.4720@.TK2MSFTNGP04.phx.gbl...
>

Replication: any way to change table schema w/o reinitializing subscriptions -

Hi all,

I'm admitedly a bit new to the world of replication, so please bear with me. I've got two SQL Server 2000 servers running in different locations. Server A does transactional replication over a push subscription to server B. If I need to make a minor change to one of the replicated tables (for example, dropping a no longer used column or changing a varchar field's length) do I need to drop the subscription, make the changes and then re-initialize the schemas and data?

For minor changes, I really hate having to knock out the site runnign off server B while the subscription is re-initialized and data is bulk copied back over. If I want to just make the changes manually on both servers will that cause problems down the line?

Any help is greatly appreciated.

tia.

-mYes, there are a number of ways to do this (run schizoid schemas), but they can be dangerous. Tampering with a subscriber schema will often force you to reinit all of the subscriptions to the affected tables.

Without knowing exactly what your configuration is, I'd only be guessing. With replication, guessing can be dangerous!

-PatP|||http://www.databasejournal.com/features/mssql/article.php/1477441 for information on replication for schema changes.

In SQL Server 7.0, if you have to change the schema of a replicated table, first you have to unsubscribe to all the publications, which are based on this table. Then, delete all the publications. Do the schema change. Republish the table and resubscribe. Whereas in SQL 2K its not required you can perform schema changes without re-defining replication.

replication/distributor problem

Hello,
I'm trying to set up transactional replication on two SQL2k Servers.
Unfortunately I stuck on the following problem:
I use 'Configure Publishing and Distribution Wizard' , I make one of the
servers (publisher) its own distributor, then I set all the paths .After
pressing 'Finish' button, the wizard tries to perform next step i.e.
'Configuring Distributor' and I get the error:
"Error 14114: '(null)' is not configured as a Distributor". Does anyone have
idea what I should do in order to solve the problem?

I tried to run procedures manually, and I get exactly the same error when I
try to execute sp_adddistributondb

Thanks,

Piotrektry this in QA

SELECT @.@.ServerName

My guess is that this returns NULL.

Now do

Exec sp_AddServer '<Name>', 'local'

Restart the SQL Server and try again

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know

"Piotrek Stachowicz" <dynamite@.poczta.onet.pl> wrote in message
news:cdllkd$5ja$1@.news.onet.pl...
> Hello,
> I'm trying to set up transactional replication on two SQL2k Servers.
> Unfortunately I stuck on the following problem:
> I use 'Configure Publishing and Distribution Wizard' , I make one of the
> servers (publisher) its own distributor, then I set all the paths .After
> pressing 'Finish' button, the wizard tries to perform next step i.e.
> 'Configuring Distributor' and I get the error:
> "Error 14114: '(null)' is not configured as a Distributor". Does anyone
have
> idea what I should do in order to solve the problem?
> I tried to run procedures manually, and I get exactly the same error when
I
> try to execute sp_adddistributondb
> Thanks,
> Piotrek