Showing posts with label tasked. Show all posts
Showing posts with label tasked. Show all posts

Wednesday, March 28, 2012

New To Replication

I am a software developer who has been tasked with setting up replication for one of our clients. I have about 1 week of experience working with replication, so any help would be appreciated.
My situation:
5 databases:
Production - All sales transactions go into here
Corporate - Used to report on everything in the Production DB
Site A - Filtered for Site A data
Site B - Filtered for Site B data
Site C - Filtered for Site C data
All connections must be two-way (Data changed at Site A most propagate back through Corporate to Production, data entered at Production -> Corporate -> Site A\B\C)
I want the Corporate DB to be the publisher and Production, Site A\B\C to be subscribers to keep the load off Production.
The issues I have are:
Filtering the data to Sites A\B\C
Default values are being stripped off columns during replication
Data is not being propagated accuratly (Data entered at production replicated to Corporate, then the data is deleted at Corporate and at Production).
I have tried several combinations of Merge and Transactional Replication and nothing works as needed.
Thanks,
David
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
David,
one topology that should solve your issues:
Production publishes everything to Corporate using merge.
Corporate publishes to SitesA-C (3 subscribers) using merge with dynamic
filters.
This setup is known as republishing, as Corporate is both a publisher and a
subscriber.
HTH,
Paul Ibison

Monday, March 19, 2012

New server name

I am tasked with bringing my Windows 2000 server which
runs SQL 7.0 into another domain as a member server. I
will have to change the name of my server also. Does this
affect SQL? I know the Services Manager refers to the
file server name and was wondering, after I change the
name, will SQL see this, or will I have to manually change
some things in SQL?Hi,
SQL 7.0 will not start after changing the Server name. You need to insert
the SQL Server CD and run setup.
This just updates the registry with the new server name and will not change
any databases.
After this start SQL server and login using Query Analyzer and execute below
commands,
sp_dropserver <old server name>
go
sp_addserver <newserver name>,local
Thanks
Hari
MCDBA
"Rick" <anonymous@.discussions.microsoft.com> wrote in message
news:0e6101c3a222$ddbface0$a501280a@.phx.gbl...
> I am tasked with bringing my Windows 2000 server which
> runs SQL 7.0 into another domain as a member server. I
> will have to change the name of my server also. Does this
> affect SQL? I know the Services Manager refers to the
> file server name and was wondering, after I change the
> name, will SQL see this, or will I have to manually change
> some things in SQL?|||SQL should recognize the new server name when you reboot or start and
stop sql services. I believe you should correct the sysservers system
table by manually running this...
sp_dropserver old_name
GO
sp_addserver new_name, local
GO
Billy|||For 7.0, you need to run setup as well.
--
Tibor Karaszi
"Billy" <bwood@.gibson.com> wrote in message
news:182d2236.0311031226.2ddcda98@.posting.google.com...
> SQL should recognize the new server name when you reboot or start and
> stop sql services. I believe you should correct the sysservers system
> table by manually running this...
> sp_dropserver old_name
> GO
> sp_addserver new_name, local
> GO
> Billy|||Thanks for the solid info Hari. Appreciate it.
>--Original Message--
>Hi,
>SQL 7.0 will not start after changing the Server name.
You need to insert
>the SQL Server CD and run setup.
>This just updates the registry with the new server name
and will not change
>any databases.
>After this start SQL server and login using Query
Analyzer and execute below
>commands,
>sp_dropserver <old server name>
>go
>sp_addserver <newserver name>,local
>Thanks
>Hari
>MCDBA
>
>
>"Rick" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0e6101c3a222$ddbface0$a501280a@.phx.gbl...
>> I am tasked with bringing my Windows 2000 server which
>> runs SQL 7.0 into another domain as a member server. I
>> will have to change the name of my server also. Does
this
>> affect SQL? I know the Services Manager refers to the
>> file server name and was wondering, after I change the
>> name, will SQL see this, or will I have to manually
change
>> some things in SQL?
>
>.
>

Wednesday, March 7, 2012

New Installation Error

Hello all.
After suffering a complete RAID failure, I am now tasked with the
responsibility of setting up reporting services again, on a new and
different machine. I had been successful getting it running last time,
so I figured this wouldn't be too much problem. The installation goes
fine, until the end, when it reports that the service wont start for
the first time.
As for information. Server2003-sp1. For the ReportServer Windows
service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
virtual directories the same, except that I've disabled SSL
connections. The Database is running locally, and for the runtime
connection credentials, I've chosen to use a Domain User Account (set
up especially for this purpose) "RSExec".
As I said, the install goes fine, but fails. The only thing I can
think of is that maybe my new RSExec user needs more permission than a
standard user. But I've read the books (Lachev, and Blackburn &
Vaughn), as well as the BOL, and I can't find any indication of what I
might be missing.
Opening the //machine/ReportServer page, I get the following error
message:
* The report server cannot open a connection to the report server
database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
Online Help
o Logon failure: the user has not been granted the requested logon
type at this computer.
The error message from the log shows:
w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
System.Web.Services.Protocols.SoapException: The report server cannot
open a connection to the report server database. The logon failed. -->
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
The report server cannot open a connection to the report server
database. The logon failed. -->
System.Runtime.InteropServices.COMException (0x80070569): Logon
failure: the user has not been granted the requested logon type at this
computer.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
pImpToken)
at
Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
userName, String domain, String userPwd)
-- End of inner exception stack trace --
Thanks for all your help. It is sincerely appreciated.
Brian AckermannDid you grant RSExec permissions to logon to SQL server? If so, can you
check to see if the user has permission to the RS database?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127830923.220944.153010@.g44g2000cwa.googlegroups.com...
> Hello all.
> After suffering a complete RAID failure, I am now tasked with the
> responsibility of setting up reporting services again, on a new and
> different machine. I had been successful getting it running last time,
> so I figured this wouldn't be too much problem. The installation goes
> fine, until the end, when it reports that the service wont start for
> the first time.
> As for information. Server2003-sp1. For the ReportServer Windows
> service I'm using account (NT AUTHORITY\NETWORK SERVICE). I've left
> virtual directories the same, except that I've disabled SSL
> connections. The Database is running locally, and for the runtime
> connection credentials, I've chosen to use a Domain User Account (set
> up especially for this purpose) "RSExec".
> As I said, the install goes fine, but fails. The only thing I can
> think of is that maybe my new RSExec user needs more permission than a
> standard user. But I've read the books (Lachev, and Blackburn &
> Vaughn), as well as the BOL, and I can't find any indication of what I
> might be missing.
> Opening the //machine/ReportServer page, I get the following error
> message:
> * The report server cannot open a connection to the report server
> database. The logon failed. (rsReportServerDatabaseLogonFailed) Get
> Online Help
> o Logon failure: the user has not been granted the requested logon
> type at this computer.
> The error message from the log shows:
> w3wp!ui!dc0!9/27/2005-08:25:37:: e ERROR:
> System.Web.Services.Protocols.SoapException: The report server cannot
> open a connection to the report server database. The logon failed. -->
> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseLogonFailedException:
> The report server cannot open a connection to the report server
> database. The logon failed. -->
> System.Runtime.InteropServices.COMException (0x80070569): Logon
> failure: the user has not been granted the requested logon type at this
> computer.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> pImpToken)
> at
> Microsoft.ReportingServices.Library.ConnectionManager.GetImpersonationToken(String
> userName, String domain, String userPwd)
> -- End of inner exception stack trace --
> Thanks for all your help. It is sincerely appreciated.
> Brian Ackermann
>|||Daniel,
Thanks for the reply.
As far as I can tell, the installer gives the RSExec user permissions
on the database. I must be missing it if there was something else.
There was a user called RSExec intalled on the database, with what
appeared to be appropriate values.
Can you be more explicit as to what settings exactly need to be set.
I'm sure its quite simple, and that I'm just not seeing it.
Thanks
Brian Ackermann|||From the look of the call stack, it appears that you are using a domain
account to talk to the RS database server. It doesn't appear that user has
permission to logon to the RS box. You should verify if that is the case.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Ackermann" <brian.ackermann@.gmail.com> wrote in message
news:1127939219.565435.135110@.o13g2000cwo.googlegroups.com...
> Daniel,
> Thanks for the reply.
> As far as I can tell, the installer gives the RSExec user permissions
> on the database. I must be missing it if there was something else.
> There was a user called RSExec intalled on the database, with what
> appeared to be appropriate values.
> Can you be more explicit as to what settings exactly need to be set.
> I'm sure its quite simple, and that I'm just not seeing it.
> Thanks
> Brian Ackermann
>