Hi,

We recently identified a performance issue with a long running query (usually around 9 seconds using an existing, different index) which is improved with the addition of a new non-clustered index.

The new index has recently been applied to the primary database and performance improved to around 1-2 seconds.  This index has also been applied to our replicated database (which has exactly the same schema, data and indexes for the table as the primary database in this case) but it is not using this new index, rather the existing, different index.

All indexes on our replicated database are applied manually rather than automatically.

We know it's using the existing, different index from looking at actual execution plans.

We've updated statistics for the table but still no improvement.

When we initially applied the index to the primary database table we ran an sp_recompile on the table, but this was a step we'd added due to previous slow running stored procs after an upgrade.  That is the only difference we can think of between the steps we've taken in creating the index and can't see why that would make a difference if we updated the statistics for the table anyway.

Can anyone offer any other checks or steps we could take to get queries to use the index (without using hints)?

Thanks

Chris

Hi there,

We are developing a system where we have an e-commerce portal through which we can sell items that are at the shops of our vendors. The website is connected to a ms sql server standard edition and has a fixed ip address. At vendors end, we are providing them a small pos software which will have ms sql express or compact edition which will be connected to internet. Also, there will be no fixed ip address at vendor's end.

My question is, in this scenario is it possible to have real time bi-directional synchronization. That is, if anything is sold on the vendor's side, it gets reflected on the central ms sql standard edition server (having fixed ip address) in real time and if anything is sold on the website it gets reflected on the vendor's panel (consisting ms sql express edition, dynamic ip address) in real time.

I would be highly thankful if someone can suggest the proper architecture for achieving the same.

Thanx in advance.

Hi,

I am performing clean installation from SQL 2008 to SQL 2012 on the same box (it won't be an upgrade). My question is how it is possible to migrate publications and subscriptions from one server to another? should I backup them or script them out, what about other replication servers involved in this? 

thank you,

Hi,

I have 12GB table with 46M records in it. My server has 16GB of memory. Im using Merge replications with dinamic filtering. Whenever replications try to replicate this table I get:

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. (Source: MSSQLServer, Error number: 1204)

"SELECT COUNT(*) FROM sys.dm_tran_locks" returns around 8,5M LOCKS at the point where the replication fails.

I assume that 16GB is not enough for this operation, which I could understand... However is there a workaround on how I could replicate in smaller batches by manipulating some replication parameters, or any other way? I really need to replicate this table without upgrading RAM.

Sql Server Agent Error: Request to run job name-pc\name-databasename-name\name-15(from User name-pc\name) refused because the job is already running from request by User sa. Changed database context to "databasename". (Microsoft SQL Server , Error: 22022).

Any Help pls?

Hi all,

I am configuring Web syncronization and I run into the above error when the

subscriber tries to syncronize. I have confirmed that the dll's are registered

on the publisher the correct Resolver entries are there via 12 entries through calling

sp_enumcustomresolvers

I have also looked here and done the changes via the "Workaround"

which is here http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/d05c0315-92c0-40b7-9f3b-0c5e8888066b

and that didnt help.

Any advise would be greatly appreciated in trying to resolve this.

Kind regards,

MMck

Dear,

Can  some one advise me and give best recommendation.

Currently at our headquarter we are having a main database and all branches are connected to it.

Now we are going to open new site and we wanted this branch to have its own database and the same data should be reapplication between HQ .

What ever there is a new update or insert in new site it should replicate to HQ and if there is insert or update in HQ the data should replicate to New site Database.

In this Scenario what Setup I should build.

The current setup is Sql server 2008 r2 Mirroring in HQ .

Which is the best practices and also suggest HA and fail over scenario. 

I have a filtered index on a merge replication enabled table, but the index alone is not getting propagated to any of the subscriber and even to the new subscriber. I also tried doing re-init but no help. And i couldn't able to find any microsoft article on this as well. 

I would appreciate the help.

---

Please remember to mark the replies as answers if they help.

- Kerobin

Hi all,

In reference to http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/d3b2987e-7391-4c35-9b65-a04068f2209c

i have a clear audit trail of a Published Table and also on the Subscriber. My investigation is showing that

for an Update being pushed from the Publisher to the Subscriber it looks like *sometimes these updates also

get logged to be Pushed Back from the Subscriber to the Publisher.

This is very confusing. 

Is there some best practice guidelines to follow to bypass this behavior?

Any advice greatly appreciated and have yourselves a great weekend:).

Kind regards,

MMck

Hi all,

I have a problem and would appreciate any advice in order to troubleshoot and address it.

I have the following setup

SQL 2005 SP3 on the Publisher and this is Merge Replication.

The Republishing Server has 1 publication for a table which uses the Automatic Identity Key Management
feature. Note that this all works great but when I try and create another Publication using the same table but filtering the data in a different way
I now run into the error "The specified automatic identity support parameters conflict with the settings in another article"[i][/i].

So as a Basic Example we have

1. First publication looking in Table_1 for a Filter to look at Company Code 1

2. Second publication looking at Table_1 for a filter to at Company Code 2

On attempting to create the second publication the above error is thrown.

Any advice on how to troubleshoot further?

Kind Regards,

MMck

Hi All,

I have problem when create new publication on SQL Server 2005. I use Windows 2008 R2 and SQL Server 2005, when i create new publication with Microsoft SQL Server Management Studio, it is no responding... and no appear pop up windows publication....

I use Antivirus "Syamantec End Point Protection... "

Please help me...

Thank's

Dear All,

Due to security reasons we are planning to change the SA password.

We are maintaining Updatable transitional replication between two servers.

As a first step, first I will change the SA password from Security—login---SA—properties.

Could please suggest me the next steps how to change the password for replication setup.

Thanks in Advance..

We're looking at setting up an environment that has a SQL Server 2012 Standard Server replicating to a Sql Server 2012 Web Edition server using merge replication. One of the reasons we're doing this is so that records can be updated from an app on a web server to the subscribing server, and data loads can be done on one the publishing server. We're also using this for DR purposes as well.

My question is, if the publishing Standard server fails, can the publication server be rebuilt and have the records that were updated while the publishing server was down, replicated back from the subscribing server? Plus, is this even possible using the web edition on one end? Would it work if I have Standard edition for each server since Web edition only supports subscriber only?

HI ,

        I want to insert rowguid manually for particular row... is it possible...?

---

mohanraj

 I have a transactional pull replication for my  SQL Server 2008 R2  environment. Publisher, distributor and subscriber are on separate instances. Is there a way to predict Distribution dB growth if  the distribution agent is stopped for an hour while log reader agent continues to push the transactions for publisher to Distribution DB.

hi,

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Source: MSSQLServer, Error number: 18452)

i am using mixed authentication mode only .when i configured the transitional replication i can connect to that db  from subscriber server .And i also checked manually i am able accesses files of other server .But i cant get where i am missing 

help me please !!!

---

naveen

I am usingmergereplication, I have problems with 2 subscribers showing this status:

 Enumerating inserts and updates in article 'LineaCred' (generation batch 1)

this happenedafter addinga new subscriber

 have currently4subscribers

100tablesare replicated as

I cansolve the problemas

syncdoes not finish

despues de un rato marca un deadlock

A query executing on Publisher 'DBCREDITO' failed because the connection was chosen as the victim in a deadlock. Please rerun the merge process if you still see this error after internal retries by the merge process.

HI,

I have created one custom conflict handler for handling the conflict while synchronization, Here I want to know the article name (Table name) where conflict came. 

I tried using -

            string tableName = publisherDataSet.Tables[0].TableName;

but it is giving - "Table",  I want actual table name .

Please suggest me how can we get actual table name.

Thanks in advance.

I have seen this posted in many places but none of the solutions seem to help me. Can someone take a look at the log and tell me why it's timing out and/or why it can't create the DB? I'm trying to copy a database from SQL 2008 to SQL2012 using SSMS 2012 on the destination server. I have tried the following:

1. Turned off all firewalls

2. Used both the SA accounts and Windows Authentication as logins for both the source and destination servers

3. Gave the service running the SQL Agent Admin rights on both servers (to make sure it's not an issue with creating the directory/DB)

I'm out of ideas. I don't want to use the Backup/Restore method since we have a large number of databases. Also, I want to keep the original database online so that we can test the new database in the new 2012 SQL cluster. Let me know if you need more info.

Thanks!

LOG

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

#Fields: event,computer,operator,source,sourceid,executionid,starttime,endtime,datacode,databytes,message
OnPreValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPreValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPostValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPostValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
PackageStart,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Beginning of package execution.

Diagnostic,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Maximum concurrent executables are set to 1.

DiagnosticEx,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,<?xml version="1.0"?><DTS:ParameterValues xmlns:DTS="www.microsoft.com/SqlServer/Dts"/>
OnPreExecute,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPreExecute,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPreValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnPostValidate,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,
OnProgress,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Task just started the execution.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connecting to server eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connecting to server eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connected to server eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connected to server eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connecting to server sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connecting to server sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connected to server sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:40 AM,5/1/2013 11:10:40 AM,0,0x,Connected to server sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring server objects to server sqlwarehouse from eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring server objects to server sqlwarehouse from eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring server objects to server sqlwarehouse from eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring server objects to server sqlwarehouse from eldacar
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login ##MS_PolicyEventProcessingLogin## already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login ##MS_PolicyEventProcessingLogin## already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login chang_bulk already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login chang_bulk already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login NICC\blake already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login NICC\blake already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login NICC\ITIP_DBO already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login NICC\ITIP_DBO already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login soojung_bulk already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Login soojung_bulk already exists in the destination server and so will not be transferred.
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferred server objects to sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferred server objects to sqlwarehouse
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring database ITIP from eldacar server as ITIP_new to sqlwarehouse server
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring database ITIP from eldacar server as ITIP_new to sqlwarehouse server
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Added data file ITIP_Data in path W:\MSSQL11.SQLWAREHOUSE\MSSQL\DATA\ITIP_new_Data.MDF to file group [PRIMARY]
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Added data file ITIP_Data in path W:\MSSQL11.SQLWAREHOUSE\MSSQL\DATA\ITIP_new_Data.MDF to file group [PRIMARY]
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Added log file ITIP_Log in path W:\MSSQL11.SQLWAREHOUSE\MSSQL\DATA\ITIP_new_Log.LDF
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Added log file ITIP_Log in path W:\MSSQL11.SQLWAREHOUSE\MSSQL\DATA\ITIP_new_Log.LDF
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring data to database ITIP_new from ITIP
OnInformation,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:10:41 AM,5/1/2013 11:10:41 AM,0,0x,Transferring data to database ITIP_new from ITIP
OnError,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,An error occurred while transferring data. See the inner exception for details.
StackTrace:    at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
StackTrace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.Management.Smo.Transfer.ExecuteStatements(SqlConnection destinationConnection, IEnumerable`1 statements, SqlTransaction transaction)
   at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
InnerException-->The wait operation timed out
OnError,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,An error occurred while transferring data. See the inner exception for details.
StackTrace:    at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
StackTrace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.Management.Smo.Transfer.ExecuteStatements(SqlConnection destinationConnection, IEnumerable`1 statements, SqlTransaction transaction)
   at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
InnerException-->The wait operation timed out
OnProgress,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,Database transfer failed for 1 database(s).
OnProgress,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,100,0x,Transfer objects finished execution.
OnTaskFailed,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,
OnPostExecute,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,eldacar_sqlwarehouse_Transfer Objects Task,{24678925-F6DC-417F-8D1B-5D8C072A3ABD},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,
OnWarning,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,-2147381246,0x,SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

OnPostExecute,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,
DiagnosticEx,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,0,0x,<?xml version="1.0"?><DTS:ProcessMemoryUsage xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:PeakWorkingSetSize>89284608</DTS:PeakWorkingSetSize></DTS:ProcessMemoryUsage>
PackageEnd,SQLWAREHOUSE,NICC\sqlagent_sqlcloud_wa,CDW_ELDACAR_SQLWAREHOUSE_SQLWAREHOUSE_12,{E1C89F80-DE05-4127-8182-0A6E11580259},{E56806A7-9858-4462-97CD-3DD1BBC358C5},5/1/2013 11:11:18 AM,5/1/2013 11:11:18 AM,1,0x,End of package execution.

I have 2 soon to be 3 customers who have identical database structures, tables, SP's all using merge replication etc they are run on their own servers I want to move them to a single web server and offer web synchronisation from there.

I know that I can combine all the data into a single database and seperate the data by company but currently there are only 2 tables which directly reference companies and then there are all the stored procedures and code.

I have tried attaching a second re-named database but their internal name prevents this

is there any other way I could try?

I am only ay a suck it ansd see stage

---

jnc