Increase of Lock Waits per minute with Mirroring

Hey All:

About a month ago I setup mirroring with our DB, High safety with automatic failover. Ever since the lock waits per minute in the DB went from maybe 2-5 per minute to 22-25 per minute. I am not sure if this was expected or what; but sometimes it spikes even higher than that.

Does this sound off the charts to anyone or normal for mirroring?

Thanks,

Let me know if you need anymore info....

What is the latency between your primary server and the backup server?

This may be normal as transactions aren't commited until after the command is sent to the backup server and the ACK is returned to the primary server. This would cause the locks to be held longer.

|||Latency has be low. If I go back to the last four hours (typical production day) it was 0-5 ms. I have seen it spike more but rarely. Mainly the lock waits were my concern, because they have certainly gone up and stayed up since mirroring started.

thanks
|||I should have been more clear. I was asking about network latency from your production server to the backup server and back. IE. Ping from one machine to the other, and multiply by two.|||oh ok, so if I ping from production server to the backup server; all four come back with less than 1ms. And if I go from the backup to the production it is the same.
|||Are your mirroring endpoints are set up with encryption. If you have encryption on and can remove it you will see a ten fold increase in transaction speed in a mirror session.|||There is a database mirroring counter "Transaction Delay" that can help you determine how much latency mirroring is adding to your transactions. Some applications can certainly notice it more than others in terms of lock waits.

Increase of Lock Waits per minute with Mirroring

Hey All:

About a month ago I setup mirroring with our DB, High safety with automatic failover. Ever since the lock waits per minute in the DB went from maybe 2-5 per minute to 22-25 per minute. I am not sure if this was expected or what; but sometimes it spikes even higher than that.

Does this sound off the charts to anyone or normal for mirroring?

Thanks,

Let me know if you need anymore info....

What is the latency between your primary server and the backup server?

This may be normal as transactions aren't commited until after the command is sent to the backup server and the ACK is returned to the primary server. This would cause the locks to be held longer.

|||Latency has be low. If I go back to the last four hours (typical production day) it was 0-5 ms. I have seen it spike more but rarely. Mainly the lock waits were my concern, because they have certainly gone up and stayed up since mirroring started.

thanks
|||I should have been more clear. I was asking about network latency from your production server to the backup server and back. IE. Ping from one machine to the other, and multiply by two.|||oh ok, so if I ping from production server to the backup server; all four come back with less than 1ms. And if I go from the backup to the production it is the same.
|||Are your mirroring endpoints are set up with encryption. If you have encryption on and can remove it you will see a ten fold increase in transaction speed in a mirror session.|||There is a database mirroring counter "Transaction Delay" that can help you determine how much latency mirroring is adding to your transactions. Some applications can certainly notice it more than others in terms of lock waits.sql

Incorrect Time Zone

I have just setup up SQL Notification Services 2005 at my workplace and running an instance of it. The problem that I am facing is with the deliveryrequesttime and sent time in the notification distribution view. These times are ahead of the server time by 5 hours. The server is set correctly to the local time and time zone. I would like to synchronize the deliveryrequesttime and senttime to the server time.

TIA

SSNS processes everything in UTC time. I'm guessing you are offset from the UTC by 5 hours.|||How do I go about solving this problem? Is there a setting that I modify?|||I understand from your original post that you'd like to make SSNS process things in accordance with your local time zone. But SSNS works in terms of UTC so that it can process scheduled subscriptions for multiple time zones.

What are you trying to accomplish? If it's for reporting purposes, you can calculate the offset.

HTH...

Joe|||

This was the concrete answer i was looking for.

Thanks

Tha

Incorrect Time Zone

I have just setup up SQL Notification Services 2005 at my workplace and running an instance of it. The problem that I am facing is with the deliveryrequesttime and sent time in the notification distribution view. These times are ahead of the server time by 5 hours. The server is set correctly to the local time and time zone. I would like to synchronize the deliveryrequesttime and senttime to the server time.

TIA

SSNS processes everything in UTC time. I'm guessing you are offset from the UTC by 5 hours.|||How do I go about solving this problem? Is there a setting that I modify?|||I understand from your original post that you'd like to make SSNS process things in accordance with your local time zone. But SSNS works in terms of UTC so that it can process scheduled subscriptions for multiple time zones.

What are you trying to accomplish? If it's for reporting purposes, you can calculate the offset.

HTH...

Joe|||

This was the concrete answer i was looking for.

Thanks

Tha

sql

Incorrect Time Zone

I have just setup up SQL Notification Services 2005 at my workplace and running an instance of it. The problem that I am facing is with the deliveryrequesttime and sent time in the notification distribution view. These times are ahead of the server time by 5 hours. The server is set correctly to the local time and time zone. I would like to synchronize the deliveryrequesttime and senttime to the server time.

TIA

SSNS processes everything in UTC time. I'm guessing you are offset from the UTC by 5 hours.|||How do I go about solving this problem? Is there a setting that I modify?|||I understand from your original post that you'd like to make SSNS process things in accordance with your local time zone. But SSNS works in terms of UTC so that it can process scheduled subscriptions for multiple time zones.

What are you trying to accomplish? If it's for reporting purposes, you can calculate the offset.

HTH...

Joe|||

This was the concrete answer i was looking for.

Thanks

Tha

Incorrect Time Zone

I have just setup up SQL Notification Services 2005 at my workplace and running an instance of it. The problem that I am facing is with the deliveryrequesttime and sent time in the notification distribution view. These times are ahead of the server time by 5 hours. The server is set correctly to the local time and time zone. I would like to synchronize the deliveryrequesttime and senttime to the server time.

TIA

SSNS processes everything in UTC time. I'm guessing you are offset from the UTC by 5 hours.|||How do I go about solving this problem? Is there a setting that I modify?|||I understand from your original post that you'd like to make SSNS process things in accordance with your local time zone. But SSNS works in terms of UTC so that it can process scheduled subscriptions for multiple time zones.

What are you trying to accomplish? If it's for reporting purposes, you can calculate the offset.

HTH...

Joe|||

This was the concrete answer i was looking for.

Thanks

Tha

Incorrect Data appearing in report

I have setup a report. I am calling the report from a page which passes parameters in a query string to the report.
The parameters are to be used in a stored procedure which the "Object Data Source" of the report refers to.
The stored procedure queries the data ina table and this data should be displayed in the report.

What actually happens is that the report appears but it has only the first record in the table but this is not the record
specified by the parameters passed to the stored procedure. It look as if the report is attaching to the correct table but
the query is not being executed properly.

Anyone any ideas how to fix this?
macca

Does ur storeprocedure return the right data when u run in SSMS or in the Data layout of ur report?

|||

Thanks for the reply Karenros but how do I test what you are suggesting.

Thanks,

macca

|||

Go to sql server ManagementStudio and then go to the database u wanna access and then click on new query.. in the new query window type in ur sproc name and give the parameters for ur sproc and u should see the results in the same window...

Or u can go to ur report in VS2005 and then click on the data part of ur report and u will see the name of the dataset and the sproc name.. next to the sproc click the exceute button and it will prompt u for parameters and after u enter them they should display the results...

Hope this helps.

Regards

Karen

|||Thanks for that Karen that works.I am getting another problem though. I am calling the report via a Response.redirect but am getting an error with the dates formats. The error message is as follows:"An error has occurred during report processing.· String was not recognized as a valid DateTime." I am calling the report and the url looks like this:· · "/PaymentReport.aspx?Section=107&DateFrom=02/10/2007&DateTo=19/10/2007". When I try the method you suggested above I must put in the DateFrom as 10/2/2007 and DateTo as 10/19/2007. The report is obviously not getting the dates in the query string in the correct format and therefore the error.

|||

How are u storing ur date time in ur database. looks like the format you are using is dd/mm/yyyy... and by any chance is the date in ur database stored as mm/dd/yyyy?

Regards

Karen

|||

Macca,

while u are giving ur date Parameter try putting it in Single quote... take a look at this code.

Declare @.reqDeldatedatetimeSet @.reqDeldate ='1/31/2007'Select OrderId, OrderDate, PlanId, RequiredDeliveryDateFrom [Order]Where RequiredDeliveryDate = @.reqDeldate

If i just @.reqDeldate as 1/31/2007 instead of '1/31/2007' nothing shows up.

 So try giving it quotes..

Regards

Karen

|||

Thanks Karen that worked.

I now have another problem. The report is not bringing back the correct results from the query. It appears to just bring back one record multiple times.

But if I run the query it brings back the correct results.

I don't know why it is doing this.

Any ideas?

macca

|||

can u pls post ur store procedure code? and have u tried refreshing the data in VS studio.. cause sometimes i have seen display the old data... and after i refresh it works fine... and try deploying it to the report server to see if it gives the correct results.

Hope this helps.

Regards

Karen

|||

Here is my Stored procedure:

CREATE PROCEDURE sproc_PaymentReports

(
@.DateFrom Datetime,
@.DateTo Datetime,
@.Status Int,
@.Section Int
)

AS

BEGIN
SELECT cheq_id, cheq_daterec, cheq_pername, cheq_amt
FROM RecCheqs
WHERE cheq_DateRec >= coalesce(nullif(@.DateFrom, ' '),cheq_DateRec) AND cheq_DateRec <= coalesce(nullif(@.DateTo, ' '),cheq_DateRec)
AND cheq_dept = coalesce(nullif(@.Section , ' '),cheq_dept)
AND cheq_added = coalesce(nullif(@.Status , ' '),cheq_added)
END
GO

How do you deploy to the report server?

macca

|||

Do u have a report server setup? if yes

then in VS go to Project and then click on properties and in the window that comes up Give a

Name for the TargetReportFolder. and in the TargetServerURL ... give http:/Either localhost or an ipaddress/ReportServer

and click ok ... for the first time the overwriteDatasources to false...but sometimes i would have to make changes to the report to the dataset so i just set it to true.

Once u set ur project properties... Go to Build -- Deploy Project name and it should prompt for a user name and password if required...

and to run ur report from the report server... go to the address that u specified in the TargetReportServerURL and then navigate to the folder name and click on the main report that runs it... and then its like .... runing it from Visual studio

Hope this helps...

Regards

Karen

|||

I don't have a report server setup so can't do any of that. This is not doing it for me at all.

In .net 1.1 I used to create reports using a Repeater and I would run the stored procedure and it would "Bind" the data to the repeater and it would work fine.

I have tried this with the ReportViewer using the following code but cannot get it to Bind:

Dim oDSAs DataSet

Dim oChequeAsNew Cheque

Try

oDS =New DataSet

oDS = oCheque.GPAssignedReport(dateFrom, dateTo, Section, Status)

If oDS.Tables(0).Rows.Count > 0Then

rptVwPayment.DataBind()

rptVwPayment.Visible =True

This code works for the repeaters in 1.1 but cannot get it to bind to report.

Any ideas, as I am ready to abandon Reports as a pack of rubbish.

macca

|||

i have used the report viewer control... but only done it using remote processing cause all my reports are located in the report server.

|||

Karen,

Thanks for all your help I got that resolved.

macca

incompatible beta components

When I try to install SQL Server 2005 I get a message that says:
SQL Server 2005 Setup has detected incompatible components from beta
versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
Remove Programs to remove these components.
I haven't installed any beta software. What step should I take next?
Daniel
Daniel
> I haven't installed any beta software. What step should I take next?
Looks strange, are you sure?
What is the version are you installing ?
Uninstall all programs that relate to SQL Server 2005 or VS .
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>
|||Did you check the add/remove programs in control panel to make sure none of
those listed components were installed? If you do see any previous versions
of those components, uninstall them. Also, restart your server before
attempting the install.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>
|||You may also want to run MsiInv to see what applications the
installer may be picking up. Sometimes the different apps or
remains of some apps don't show up in Add/Remove Programs.
The installer can pick up on those and throw the error you
are getting. MsInv should pick that up. For more info, check
the following article and follow the links in that article:
http://blogs.msdn.com/astebner/archi...30/487096.aspx
-Sue
On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
<Mahonri@.cableone.net> wrote:

>When I try to install SQL Server 2005 I get a message that says:
>SQL Server 2005 Setup has detected incompatible components from beta
>versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
>Remove Programs to remove these components.
>I haven't installed any beta software. What step should I take next?
>Daniel
>
|||I've done that. It is strange to me too. Has no one else ever run into
this problem? I wasn't able to find anything in knowledge base.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:emkY1hj2GHA.4924@.TK2MSFTNGP05.phx.gbl...
> Daniel
> Looks strange, are you sure?
> What is the version are you installing ?
> Uninstall all programs that relate to SQL Server 2005 or VS .
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>
|||I've done those things. There are not any of those components installed. I
even uninstalled .NET 1.1. I considered uninstalling .NET 2.0. There are a
lot of Windows Server 2003 Hotfixes. I didn't think they would matter since
I just installed Windows Server 2003 SP1. I wonder if I need to get a newer
version of SQL Server 2005.
Daniel
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:%23uI3TUk2GHA.1292@.TK2MSFTNGP03.phx.gbl...
> Did you check the add/remove programs in control panel to make sure none
> of those listed components were installed? If you do see any previous
> versions of those components, uninstall them. Also, restart your server
> before attempting the install.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>
|||After using MSIInv.exe, I could not find anything beta.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:atjrg2hq70ob5vdvnldp6e6fpabh3cc5pj@.4ax.com...
> You may also want to run MsiInv to see what applications the
> installer may be picking up. Sometimes the different apps or
> remains of some apps don't show up in Add/Remove Programs.
> The installer can pick up on those and throw the error you
> are getting. MsInv should pick that up. For more info, check
> the following article and follow the links in that article:
> http://blogs.msdn.com/astebner/archi...30/487096.aspx
> -Sue
> On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
> <Mahonri@.cableone.net> wrote:
>

incompatible beta components

When I try to install SQL Server 2005 I get a message that says:
SQL Server 2005 Setup has detected incompatible components from beta
versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
Remove Programs to remove these components.
I haven't installed any beta software. What step should I take next?
DanielDaniel
> I haven't installed any beta software. What step should I take next?
Looks strange, are you sure?
What is the version are you installing ?
Uninstall all programs that relate to SQL Server 2005 or VS .
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>|||Did you check the add/remove programs in control panel to make sure none of
those listed components were installed? If you do see any previous versions
of those components, uninstall them. Also, restart your server before
attempting the install.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>|||You may also want to run MsiInv to see what applications the
installer may be picking up. Sometimes the different apps or
remains of some apps don't show up in Add/Remove Programs.
The installer can pick up on those and throw the error you
are getting. MsInv should pick that up. For more info, check
the following article and follow the links in that article:
http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx
-Sue
On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
<Mahonri@.cableone.net> wrote:
>When I try to install SQL Server 2005 I get a message that says:
>SQL Server 2005 Setup has detected incompatible components from beta
>versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
>Remove Programs to remove these components.
>I haven't installed any beta software. What step should I take next?
>Daniel
>|||I've done that. It is strange to me too. Has no one else ever run into
this problem? I wasn't able to find anything in knowledge base.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:emkY1hj2GHA.4924@.TK2MSFTNGP05.phx.gbl...
> Daniel
>> I haven't installed any beta software. What step should I take next?
> Looks strange, are you sure?
> What is the version are you installing ?
> Uninstall all programs that relate to SQL Server 2005 or VS .
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>> When I try to install SQL Server 2005 I get a message that says:
>> SQL Server 2005 Setup has detected incompatible components from beta
>> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
>> and Remove Programs to remove these components.
>> I haven't installed any beta software. What step should I take next?
>> Daniel
>|||I've done those things. There are not any of those components installed. I
even uninstalled .NET 1.1. I considered uninstalling .NET 2.0. There are a
lot of Windows Server 2003 Hotfixes. I didn't think they would matter since
I just installed Windows Server 2003 SP1. I wonder if I need to get a newer
version of SQL Server 2005.
Daniel
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:%23uI3TUk2GHA.1292@.TK2MSFTNGP03.phx.gbl...
> Did you check the add/remove programs in control panel to make sure none
> of those listed components were installed? If you do see any previous
> versions of those components, uninstall them. Also, restart your server
> before attempting the install.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>> When I try to install SQL Server 2005 I get a message that says:
>> SQL Server 2005 Setup has detected incompatible components from beta
>> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
>> and Remove Programs to remove these components.
>> I haven't installed any beta software. What step should I take next?
>> Daniel
>|||After using MSIInv.exe, I could not find anything beta.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:atjrg2hq70ob5vdvnldp6e6fpabh3cc5pj@.4ax.com...
> You may also want to run MsiInv to see what applications the
> installer may be picking up. Sometimes the different apps or
> remains of some apps don't show up in Add/Remove Programs.
> The installer can pick up on those and throw the error you
> are getting. MsInv should pick that up. For more info, check
> the following article and follow the links in that article:
> http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx
> -Sue
> On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
> <Mahonri@.cableone.net> wrote:
>>When I try to install SQL Server 2005 I get a message that says:
>>SQL Server 2005 Setup has detected incompatible components from beta
>>versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
>>and
>>Remove Programs to remove these components.
>>I haven't installed any beta software. What step should I take next?
>>Daniel
>

incompatible beta components

When I try to install SQL Server 2005 I get a message that says:
SQL Server 2005 Setup has detected incompatible components from beta
versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
Remove Programs to remove these components.
I haven't installed any beta software. What step should I take next?
DanielDaniel
> I haven't installed any beta software. What step should I take next?
Looks strange, are you sure?
What is the version are you installing ?
Uninstall all programs that relate to SQL Server 2005 or VS .
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>|||Did you check the add/remove programs in control panel to make sure none of
those listed components were installed? If you do see any previous versions
of those components, uninstall them. Also, restart your server before
attempting the install.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Daniel" <Mahonri@.cableone.net> wrote in message
news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
> When I try to install SQL Server 2005 I get a message that says:
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add
> and Remove Programs to remove these components.
> I haven't installed any beta software. What step should I take next?
> Daniel
>|||You may also want to run MsiInv to see what applications the
installer may be picking up. Sometimes the different apps or
remains of some apps don't show up in Add/Remove Programs.
The installer can pick up on those and throw the error you
are getting. MsInv should pick that up. For more info, check
the following article and follow the links in that article:
http://blogs.msdn.com/astebner/arch.../30/487096.aspx
-Sue
On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
<Mahonri@.cableone.net> wrote:

>When I try to install SQL Server 2005 I get a message that says:
>SQL Server 2005 Setup has detected incompatible components from beta
>versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add and
>Remove Programs to remove these components.
>I haven't installed any beta software. What step should I take next?
>Daniel
>|||I've done that. It is strange to me too. Has no one else ever run into
this problem? I wasn't able to find anything in knowledge base.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:emkY1hj2GHA.4924@.TK2MSFTNGP05.phx.gbl...
> Daniel
> Looks strange, are you sure?
> What is the version are you installing ?
> Uninstall all programs that relate to SQL Server 2005 or VS .
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>|||I've done those things. There are not any of those components installed. I
even uninstalled .NET 1.1. I considered uninstalling .NET 2.0. There are a
lot of Windows Server 2003 Hotfixes. I didn't think they would matter since
I just installed Windows Server 2003 SP1. I wonder if I need to get a newer
version of SQL Server 2005.
Daniel
"Narayana Vyas Kondreddi" <answer_me@.hotmail.com> wrote in message
news:%23uI3TUk2GHA.1292@.TK2MSFTNGP03.phx.gbl...
> Did you check the add/remove programs in control panel to make sure none
> of those listed components were installed? If you do see any previous
> versions of those components, uninstall them. Also, restart your server
> before attempting the install.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Daniel" <Mahonri@.cableone.net> wrote in message
> news:%235s4nOf2GHA.4632@.TK2MSFTNGP03.phx.gbl...
>|||After using MSIInv.exe, I could not find anything beta.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:atjrg2hq70ob5vdvnldp6e6fpabh3cc5pj@.
4ax.com...
> You may also want to run MsiInv to see what applications the
> installer may be picking up. Sometimes the different apps or
> remains of some apps don't show up in Add/Remove Programs.
> The installer can pick up on those and throw the error you
> are getting. MsInv should pick that up. For more info, check
> the following article and follow the links in that article:
> http://blogs.msdn.com/astebner/arch.../30/487096.aspx
> -Sue
> On Sat, 16 Sep 2006 19:53:12 -0500, "Daniel"
> <Mahonri@.cableone.net> wrote:
>
>

Including Views in Replication

I have a three server peer-to-peer replication setup that includes articles for tables and views. As I understand the BOL, scheme changes -- which I take to mean changes, amont other things, changes in the design of a table or view -- should automatically replicate to the other servers in the topology. Here are my quesitons:

When including a view as part of the publication, what is it, exactly, that is getting replicated? If all the tables supporting a given view are being replicated, and the view exists on all three boxes, whatelse, besides the view schema (and changes thereto) is being replicated?

Secondly, if in fact schema changes are replicated, why can't I modify a view that is part of a publication? When I try to make a change to such a view, I get a server timeout message, every single time. When I remove the view from the publication, I can make the modification with no trouble. What does replicating schema changes mean if I can't make changes to the schema?

Thanks for any enlightenment on this.

Randy

In general, when views are replicated, the schema definition of the view object is actually what gets replicated. After initial sync, there are no data changes tied to a view.

In non-peer-to-peer transactional replication, view schema changes are propagated from the publisher to the subscribers automatically. i.e. A view schema change could be changing the list of columns included in the view select statement.

Since you have a peer-to-peer topology set up there are more restrictions to consider. Check out the General Considerations under Peer-to-Peer replication in SQL Server 2005 Books Online. One of the restrictions is that any schema changes require the peer-to-peer topology to be quiesced (stopping activity on published tables at all nodes and ensuring that each node has received all changes from all other nodes).

Hope this helps,

Tom

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

the resultset and content of the view can only be replicated if it is "indexed" if the view is not index the only thing that gets replicated is the view definition.

|||

Hi Randy,

I am interested to know more about your second issue (timeout when modify a view). Could you give me more details on your issue? For example, what statement do you use to modify a view, what is the origional view definition and what is the error message?

Thanks,

Peng