Refracted Paladin's questions

I have setup a D3 VM running Windows 10 on my Azure account. Unfortunately the Disk speed, on both the C (200GB) and D (100GB Temp) are EXTREMELY low. Less than 1MB/s when viewed through Task Manager while copying over a large folder structure containing about 16000 items.

To be honest I'm not even sure what to try...I guess my plan will be to create a new vhd drive, attach it, and see how it performs but I'm not real hopeful.

I read through this post --> Slow disk performance on Azure Virtual Machine

and

this post --> http://azure.microsoft.com/blog/2014/10/06/d-series-performance-expectations/

They both reference "throttling" which I understand but what I am seeing must be something different as I never approach the level it states of 96MB/s write.

Is this just common knowledge or is it possible I have something configured wrong? A Windows 10 VM bug maybe? I have verified that I did, in fact, chose D3 for my VM size which includes a 200GB local SSD.

Any suggestions on what I can check or try next?

EDIT

Some further info. Here is a screenshot of my Disk Read/Write from the Azure Portal for the last 24 hours.

Not a 100% sure this belongs here but here goes nothing. What is the relationship between EWS versions and Exchange. I want to use EWS 1.2 which says Exchange 2007 SP2 or up. What I am asking, I guess, is the EWS version tied to the Exchange version or can I get Exchange 2007, no SP's, work with EWS 1.1 or 1.2?

I am trying to setup our replication with a republisher. We, unfortunately, have some tables with an int PK IDENTITY and I am getting the following error when trying to create the publication.

SQL Server Management Studio could not create article 'tblAdminBusinessType'. (New Publication Wizard)

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The republisher's republishing range obtained from its publisher is not large enough to allocate the specified @pub_identity_range.
The article 'tblAdminBusinessType' could not be added to the publication 'Stage_Connect'.
Changed database context to 'Stage_Connect'. (Microsoft SQL Server, Error: 20660)

I changed the Publisher range size to 100000 and the Subscriber range size to 100. What I am not understanding is why this even matters, this table is marked as download only at both the Primary Publisher and the Re-Publisher. It can't be updated anywhere BUT directly on the Primary so what's the issue.

Secondly, how do I overcome this? Do I just keep massaging the numbers till it works? What, specifically, is it looking for?

Thanks

Thank you,

I have a table that has grown quite large that we are replicating to about 120 subscribers. A FK on that table does not have an index and when I ran an Execution Plan on a query that was causing issues it had this to say -->

/*
Missing Index Details from CaseNotesTimeoutQuerys.sql - mylocal\sqlexpress.MATRIX (WWCARES\pschaller (54))
The Query Processor estimates that implementing the following index could improve the query cost by 99.5556%.
*/

/*
USE [MATRIX]
GO
CREATE NONCLUSTERED INDEX [<Name of Missing Index, sysname,>]
ON [dbo].[tblCaseNotes] ([PersonID])

GO
*/

I would like to add this but I am afraid it will FORCE a reinitialization. Can anyone verify or validate my concerns? Does it even work that way or would I need to run the script on each subscriber?

Any insight would be appreciated.

I have a Win Form, Data Entry, application that uses 4 seperate Data Bases. This is an occasionally connected app that uses Merge Replication (SQL 2005) to stay in Sync. This is working just fine. The next hurdle I am trying to tackle is adding Filters to my Publications.

Right now we are replicating 70mbs, compressed, to each of our 150 subscribers when, truthfully, they only need a tiny fraction of that. Using Filters I am able to accomplish this(see code below) but I had to make a mapping table in order to do so. This mapping table consists of 3 columns. A PrimaryID(Guid), WorkerName(varchar), and ClientID(int).

The problem is I need this table present in all FOUR Databases in order to use it for the filter since, to my knowledge, views or cross-db query's are not allowed in a Filter Statement.

What are my options?

Seems like I would set it up to be maintained in 1 Database and then use Triggers to keep it updated in the other 3 Databases. In order to be a part of the Filter I have to include that table in the Replication Set so how do I flag it appropriately.

Is there a better way, altogether?

SELECT <published_columns> FROM [dbo].[tblPlan] WHERE [ClientID] IN (select ClientID from [dbo].[tblWorkerOwnership] where WorkerID = SUSER_SNAME())

Which allows you to chain together Filters, this next one is below the first one so it only pulls from the first's Filtered Set.

SELECT <published_columns> FROM [dbo].[tblPlan] INNER JOIN [dbo].[tblHealthAssessmentReview] ON [tblPlan].[PlanID] = [tblHealthAssessmentReview].[PlanID]

How do I, properly, ALTER a StoredProcedure in a SQL 2005 Merge Replication?

I just need to add a Column. I already successfully added it to the Table and I now need to add it to a SP. I did so but now it will not synchronize with the following error -->

Insert Error: Column name or number of supplied values does not match table definition. (Source: MSSQLServer, Error number: 213)

Add my comment below here for easier viewing

Yes the table change was already replicated. THEN the Stored PRocedure quit working as the columns were off so I did an ALTER on the stored procedure and tried to replicate that. Now it won't sync

I need to add a couple of columns to a table that is a part of a replication set. It is not a constraint coulumn or a part of any article filters and it allows NULL. I have a pretty good idea that I can run this --> ALTER TABLE tblPlanDomain ADD ReportWageES VARCHAR (100) NULL

and NOT force all my clients to reinitialize but I was hoping for some reassurance. Can anyone verify this one way or the other for me?

Thanks,

Edit: Addtnl Info

This is what I am talking about --> http://msdn.microsoft.com/en-us/library/ms151870.aspx

It would seem, based on that, that the answer to my question is NO but I would still like a human confirmation.

I have Merge Replication set up with a SQL 2005 Publisher/Distributor and roughly 100 SQL 2005 Express Subscribers. Everything was working fine for months and now all of a sudden everyone is getting the below errors.

I have been Googling around but to no avail. Can anyone offer some insight? I even tried deleting a user's Subscription. I also tried running -->

sp_adjustpublisheridentityrange @publication='MyDB'

Anyway, here are the errors -->

Error messages:
The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identit (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199417)
Get help: http://help/MSSQL_REPL-2147199417
Not enough range available to allocate a new range for a subscriber. (Source: MSSQLServer, Error number: 20668)
Get help: http://help/20668
Failed to allocate new identity range. (Source: MSSQLServer, Error number: 21197)
Get help: http://help/21197

I have a "working" Replication Set in SQL 2005 that we use in house to our users at remote branches on SQL Express 2005. I want to apply a filter to our biggest Set to help minimize the bandwidth impact. What I am asking is what considerations do I need to take into account before throwing a filter on there. Will it cause any issues I should be aware of? Does it affect compression adversely. Will everyone need to reinitialize after applying it?

Any heads up or insight would be appreciated.

Thanks,

EDIT

Here is a snapshot showing where the Compression setting is that I am talking about.

Also, I could include a shot of the zipped snapshots if necessary.

Thanks for the help.

I have a Replication Set that we use in Merge Replication(SQL 2005). I am trying to figure out how to apply a Filter of Top 2 to a table.

Also, is there a way to set up a Filter so that it trickles down to sub-tables or would I need to handle that differently?

What I am looking at is a Database of Plans that I am Replicating to our users' laptops. I would like to only Replicate the last two Plans and only replicate the associated data for those two plans. Example, there is a Medication table that lists all the Medication associated to a certain Plan. I would only want to replicate the rows on the Medication table that are tied to one of the Top 2 plans.

I am not sure how I should go about this. I see the Filter option in the Publication Properties but it is by table and I don't seem to have the option of Top 2.

I have Merge Replication set up at our company with a central SQL 2005 as the Publisher/Distributor and the clients are all SQL 2005 Express.

In our remote branches we are having difficulty with the initial sync time. The database is ~2GB and is taking well over an hour for that first run. In troubleshooting this I noticed that I can specify an alternate Snapshot location and then optionally compress that.

I tried this(compressing) and it compresses it significantly but I am wondering what I should be aware of when turning this on. I notice it is a single .cab file in compressed form versus all the individual script files of before.

• What are the catches?

• Why wouldn't you always use the compressed format?

• If both are left checked, default and alternate compressed, how do I tell it to use one or the other?

I have a SQL 2005 Standard*(Publisher/Distributor)* to SQL 2005 Express*(subscriber)* Replication Topology. I deleted(thru SSMS) a table and added a row to a different table. I then ReInitialized All with a Generate New Snapshot option and then ran my Subscribers Sync() Procedure.

I now get the below errors and I have no flippin idea what I should do about them...

Error messages:
The schema script 'tblCaseNotes_3.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
Get help: http://help/MSSQL_REPL-2147201001
Could not drop object 'dbo.tblCaseNotes' because it is referenced by a FOREIGN KEY constraint. (Source: MSSQLServer, Error number: 3726)
Get help: http://help/3726

tblCaseNotes is the Primary table so I don't know why it is trying to drop it...

I would like to add the information from my Production DB to my Stage DB. I have a BAK of the Production DB and could just restore from that on Stage but I am concerned of the impact Merge Replication will have on that.

Let me explain further; I have 15 users testing a sometimes connected app internally. The structure is that there is a Local SQL Express on each system subscribing to the Stage SQL 2005 server with Pull Subscriptions. The Stage server acts as Publisher and Distributor. A request has been made by the testers to use "Real" data. If I just restore the BAK's from production to my Stage instance what will happen to my Replication Sets? When the Local DB's try to Sync Up will they "FREAK OUT" because all the GUIDS have changed?

My thought was to restore the Production DB to the Stage Server under a different name and then DELETE the contents of, say, tblPerson and run a INSERT INTO from the Production tblPerson to the, now empty, Stage tblPerson.

I would like thoughts and suggestions on both.

Would restoring from the BAK's cause the end of the world

and/or

is my second solution a viable alternative?

Do I even need to do that much? Can I delete the contents of tblPerson(Stage) and then do a Cross DB SELECT INTO from tblPerson(Production) to the Stage counterpart?

Mostly I am curious/concerned of the impact this will have on my existing Subscriptions.

Our IT dept is going to use 7rc1**(7100)** 64 bit.

Unfortunately we are having an issue with OfficeScan. On install attempt it is saying we need to be member's of Administrators. I double checked and we are. Also, UAC is turned off. We were able to use it under build 7000 of the BETA but now, nadda.

An there site, HERE, it states that they*(will??)* support Windows 7.

Has anyone else experienced this? Thoughts on a fix?

EDIT 1

I have gotten past the privledges issue but I am now getting an "incompatible driver" warning. I triple checked and it is stated that TrendMicro supports 7 and I even found a few (unreachable) references to users who have it running.

Is there anything else I should check? How do I verify that my components are all up to date?

Ideas?