.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Post New Web Links

Copy production farm to staging environment

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :SharePoint

What is the best approach to set up a staging environment based on production farm? I'd like to image the WFE prod machine since I have lots of add-on and custom code installed in Prod. It will take long time to do a clean install.

We have production farm with two WFE, one App and a SQL cluster.

We are going to set up a staging environment as much similar as possible with Prod.

1. The staging will be in separate domain with separate AD etc.

2. I can't move all the production content DB to staging cause the DB is huge.

3. I'd like to combine WFE with app and use two servers (one WFE and one SQL) in the staging farm.


Thanks in advance!!





If you get confused, listen to the music play...

View Complete Post

More Related Resource Links

How to copy table data from test to production database

I'm using SQL Server 2008 R2 and I'd like to copy all data rows from one table of a test database to the identical table in a production database. The primary key of the table is referred to by other tables so a DELETE followed by a number of INSERTs won't do it because of referential integrity issues. What is the best method to replace the data rows in the destination database with the values from the source database? Thanks, Guido

Using a shared cache in a Web farm environment for detecting replay attacks in WCF

Hello, I'm trying to figure out how to implement a replay attack detection mechanism with WCF in a web farm scenario. WCF provides such detection mechanism by using a nonce cache. Correct me if I'm wrong, but the only way to ensure to prevent this attack in a message security and web farm scenario is by using a nonce cache shared across the servers (i.e.: AppFabric distributed cache). In WSE3.0, it used to be possible to provide nonce cache custom implementations http://msdn.microsoft.com/en-us/library/ff647945.aspx but there doesn't seem to be any way to do so in WCF (No configuration options, besides I found with Reflector that the NonceCache class is marked as both sealed and internal..) Any thoughts?

Making a copy of WSS3.00 from Production server to Development.

Dear All, I have a WSS3.0 production server which use MSSQL2008 database on Same box.Now I am planning to install a new server for developement purpose with same settings as production.Is it possibile to make a copy of production WSS on new Development server? It would be a great help if somebody can explain me the steps how to configure a copy of datas from Productin to Development incase if this option works!   Thanks to all in advance Regards Jo

BCS: Best practice of Toggling external content types between staging and production databases



Environment :
Sharepoint 2010
using BCS to point to external database
create two Secure Store Application ids , one with production credentails and another with staging credentails

I have several external content types (ECT) using an external system(ES) pointing to staging databases.
Now i want to change only one of my ECT to point to production DB but suprisingly the only way i could achieve this was by modifying the ES that all the other ECT are using, this is not practicaly because this makes all the ECTs point to production and not just the one that i want.

Question is how can i have different ES and how can i make only one ECT out of all the ones to point to production, i tried using the "Switch connected systems" but did not like it and below are the details:

Created a new ECT pointing to production which would show the ES being used in BCD services and then i  used the "Switch Connected Ssytems" option under designer to switch the staging ECT to the production ES. Dos the job but the problem is that if there are no ECT pointing to staging ES then it does not appear under BCS services which mean neither can i switch my ECT back to it nor would it be available when i am creating new ECT whch need to point to staging.

Hope i was clear, please suggest how to handle this sit

Clone production Sharepoint 2010 server to Developmet environment - steps? help?


Greetings all,

I'd really appreciate some thoughts and suggestions about how to make a clone of our Sharepoint 2010 Production environment that we can use for testing and development.

At the moment, we are likely to have two different servers (Production is a much more expensive, powerful server) for the scenarios; so if we make a direct clone, the Windows OS files would be upset.

Would it be enough to simply copy the Windows Shared files into the Dev system (taking all modifications with it) and the db into a cloned db?

If not, what are the things we'll have to consider, and/or has anyone accomplished this yet?

Thanks for your tips and suggestions!


Install SharePoint 2010 in a farm environment


Recently for one of my project, I had a requirement to install SharePoint on a farm environment. I had a walkthrough with technet site and completed the installation. I thought share my scenario so that somebody with similar requirement may find this useful.

First of all, I had 2 servers for the implementation. So I have decided to dedicate one server for database and another for Sharepoint installation.

The server names are SP2010_DB (for database) and SPPortal (for sharepoint). Both are joined to the domain. For the sake of this article, I am mentioning the domain as SP2010FARM.

I have used the following user accounts for the installation.

User Account


Server roles required


-Sql Server service account

- domain user account

best practise for creating staging environment


I am trying to create a staging environment which is the same configuration as production (1 WFE, 1 SQL DB, 1 APP, and Active Directory) but on a separate network. 

So we can have servers in both staging and production has the same exact names.  From time to time, I can refresh the production server farm to staging easily. I was told this is the best practice from Microsoft.

Does anyone who where I can find those related information and instructions to build such kind of staging environment?

Thanks in advance,



Solution Deployment failed in Server Farm - Some of the files failed to copy during deployment of th


Hi guys,

I created a solution package in my development environment that works well. When I try to deploy it in a test environment that is a farm with two web front end(card0023 / card0024) servers and a application server(where I have the central administration / card0027) I got the error bellow:

Deployment Status: Error
Deployed To: None
Last Operation Result: Some of the files failed to copy during deployment of the solution.
Last Operation Details: CARD0023: http://card0027:11000/ : The solution was succesfully deployed.
    CARD0027: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0023: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0024: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0027: http://card0027:11000/ : SharePoint - 11000 : Error: The web.config is missing from this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\11000\web.config. 
Someone can help me?


André Rentes

Best way to create a deployment farm from a staging farm?


After creating a staging farm, configuring the service applications, creating web apps, site collections, sites, masterpages, workflows, content, etc what is the best way to create a deployment farm from all this?

In the deployment farm the host names will be different, the base url will be different, the sql server will be different, but everything else should be the same. I know I can export the site collections and import them into the deployment farm but I would be leaving behind the service app configurations. On the other hand a full farm backup and restore might bring stuff I don't want

Any advice?

Killing SQL Server Session as a normal cancelation way in production environment



I have a problem, I'm planning to implement a solution for cancelling queries that could be risky and I need some expert advice. 

I'm using a custom data access .net assembly to execute all queries in the database, and now I've been asked to implement some sort of cancelling functionallity, so if the user press the cancel button, without knowing exactly what query is being executed (usually long lasting queries) it has to be cancelled. I can use the Kill sentence, but the problem is that I need to know which process to kill.

What I'm planning is the following...

As I can control every query executed, I can add a GUID as a comment at the end of each query that could be cancelled, so If the code tries to run the following query "Select top 1000000 from BigTable", I add the comment guid to the sentence ("Select top 1000000 from BigTable --CancelGUID:1234-3456-5678-7890")

Then I provide a method that given a CancelGUID I kill every sql server session that contains that GUID, I get all session with the following sentence:


SELECT req.session_id

FROM sys.dm_exec_requests req

CROSS APPLY sys.dm_exec_sql_text(sql_handle) AS sqltext

WHERE sqltext.text like '%CancelGUID:1234-3456-5678-7890%' 



And then execute Kill for each session_

Deploying Publishing SharePoint site from development to test and production environment.




I have created a Publishing Site in SharePoint 2010, with pages created from custom page layouts, content types and Publish Content areas which I have created using SharePoint Designer 2010.

Also, I created custom Lists, Libraries and workflows in my development environment.

I want to replicate the site in test/production environment.

Can you please suggest me the best way to package all, along with custom site settings from development environment so that I can migrate small changes to test/ production environment later also without creating .wsp as I have access to SharePoint designer 2010 only.

Abhijit Sil

.NET 4: Windows Workflow Foundation Production Environment footprint


Hi There,

We are currently an ISV evaluating WF4 for use as a Rules/Workflow engine, possibly intending to use the 'Forward-chaining' rules engine from WF3 in WF4. We currently have no WF assets.

We need to understand what the production environment footprint would be for WF4 and/or WF3.

I cannot find any useful info easily, so my questions are as follows,

1. What Server versions support WF4/3? W2003, W2008 etc

2. If I host my workflows in IIS what version of IIS will I need?

3. I have not got too far into WF yet, but I assume there are various datastores, what is the minimum version of SQL server I would need?

Thanks for you help

How to deploy ssis Packages to production Environment


Hi All,

I have a few questions regarding ssis package deployment to production environment.

In order to deploy already developed packages ...These are the things I am following...Please confirm whether I am following the correct approach...or not.. If not please let me know the exact process..

First of all I am generating the scripts for databases...corresponding tables,views and stored procedures..

Once the scripts are ready... I am executing those scripts in production environment.

After that I am adding all of my developed packages to production environment BIDS Platform. Then I am running these packages in production environment (All connection strings are updated in the configuration file)...by changing the Configuration file..

Then I am scheduling all of these packages through SQL SERVER JOB AGENT.....

Is this the right approach ...? Please let me know ASAP...







Dashboards appear slower in Production than in Development environment


Dashboards were created using PerformancePoint dashboard designer and were published to SharePoint Development environment. A backup of Devl site collection was taken and restored in Production. The dashboards appear to open slower in Production (close to a minute) than in Development (less than 5 secs) for the first time only. Subsequent response times are similar between Devl and Prod. The same code is executed in both environments.

Diferences between the two environments:
1. Development uses disk drives whereas Prod uses SAN drive.
2. Though the architecture (mentioned below) is different between Devl and Prod, the memory of the SharePoint, BI servers is the same - 64GB.

Development environment: There are two servers in the farm:
1. Windows 2008 x64 R2 server Enterprise, SQL 2008 R2 Enterprise with SSIS and SSAS, DBMS.
2. Windows 2008 x64 R2 server Enterprise, Excel services, PerformancePoint service, SQL 2008 R2 with SSRS, SharePoint Server 2010.

Production environment: There are multiple servers in the farm:
Business Intelligence:
1. Active/Passive SQL cluster with Windows 2008 x64 R2 server Enterprise, S

Visual Web Developer 2010 Express "Copy Web Site" using different login


I created a site and am trying to grant another pesron access to upload changes to it without giving them my super-user login.

I made a login for her but I can't test whether it works or not because no matter how much I "disconnect" in the Copy Web Site page of VWD 2010, reconnecting to the same site always logs in as my superuser account without prompting me for a login again.

How do I test is the account it set up correctly before having her try to upload to it?    I want to force the login to remote site dialog to pop up again to test her account.

Any ideas?

Bulk Copy From Datatable To SQL Server Table


 I have read the data of a excle file and captured the data into the dataset to a datatable, now that data is to be inserted into a SQL Server table using bulk copy option. I am using -

 public bool BulkEnterData(DataTable dt, string tblName)
        SqlBulkCopy bulk = new SqlBulkCopy(con);
        bulk.DestinationTableName = tblName;

        return true;

ERROR Getting-
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.) 

How to resolve the above problem or any other solution is available.


CLR Inside Out: Production Diagnostics Improvements in CLR 4


The Common Language Runtime (CLR) 4 includes new APIs that expand diagnostic support toward the production end of the spectrum. We explain how the debugging APIs support dump debugging for application crash and hang scenarios and make it easier to detect when hangs are caused by multi-threading issues.

Jon Langdon

MSDN Magazine May 2010

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend