As you may recall from my Not only is SBSC staying, it is THE Small Business designation in the Microsoft Partner Network (MPN) post, the Microsoft Small Business Specialist designation will continue to be the way that Microsoft partners can demonstrate their focus and skills in serving the needs of small businesses.  Just like with the Gold and Silver level competencies in the Microsoft Partner Network, it is important for partners looking to renew their enrollment in the Microsoft Partner Network with the Small Business Specialist designation ensure they are aware of the requirements necessary to meet in order to ensure you will be able to re-enroll and maintain their Small Business Specialist designation. 

For those of you looking to renew your membership in the Microsoft Partner Network with the Small Business Specialist designation, I am posting up this Step-By-Step guidance on how to go about doing this in order to help make the process as easy to follow for you as possible.

1. Build your plan:

• Review the new requirements for the Small Business Specialist Community, as well as the new Midmarket Solution Provider competency.
• If you are unclear which membership opportunity or competencies are best for your business, visit the Microsoft Partner Network Advantage as your first step.

• Check your SBSC membership status: (After October, SBSC status in PMC will be in a new place)

• Log onto the Partner Membership Center, click Other Programs Summary and scroll down to the Small Business Specialist Community section.
  

- Click on the image to the right to see full size.  This shows you where you will find the “Small Business Specialist Community”

• If you need a qualifying exam, use the following:

• SBSC requirements page for links to qualifying exams, course prep and product tests
• Exam Voucher Offers to get up to 30% off the cost of exams
• Click to Chat with an expert regarding specific exam questions

• If you need the Small Business Sales and Marketing Skills Assessment:

• Click here to take the assessment (note: starting in October 2010 there will be a new Small Business Sales & Marketing Skills Assessment)
• Click here to access the SBSC Learning Path to prep for the assessment and/or qualifying exams

• Obtain either:

• Action Pack subscription

• Action Pack Solution Provider
• Action Pack Development and Design

• A silver or gold competency (Click here to view all Microsoft Partner Network competency opportunities)

• Automatic Enrollment

• Upon meeting the program requirements, each location will be automatically enrolled in the Small Business Specialist Community.
• Individuals designated as administrators of your partner profile will be notified each time a location becomes active in this community.

One note from a timing perspective, we are talking about your re-enrollment in the Microsoft Partner Network here, which means that the date that you will need to meet the updated requirements for the Small Business Specialist designation by will be your anniversary date in the Microsoft Partner Network, not the initial launch date of the Microsoft Partner Network.  So if your anniversary date is January 31, 2011, then you have until then to meet the requirements for the Small Business Specialist designation.

• For those of you looking to achieve a Silver level competency in the Microsoft Partner Network, you may want to take a look at my: Silver Competency Step-by-step checklist to re-enrollment in Microsoft Partner Network post.
• For those of you looking to achieve a Gold level competency in the Microsoft Partner Network, you may want to take a look at my: Gold Competency Step-by-step Checklist to Re-enrollment in Microsoft Partner Network post.

I hope this step-by-step guide helps you in your process to reenroll in the Microsoft Partner Network with the Microsoft Small Business Specialist designation.

Thank you and have a wonderful day,

Eric Ligman – Follow me on TWITTER, LinkedIn, and RSS and see “What I’m thinking”
Global Partner Experience Lead
Microsoft Worldwide Partner Group
This posting is provided "AS IS" with no warranties, and confers no rights

 

In  Branching and Team Project Guidance … looking for “your” input! we started a discussion on the new branching scenarios and what the rangers are planning to add to the existing Branching Guidance (http://tfsbranchingguideiii.codeplex.com) and the Architecture Tooling Guidance (http://vsarchitectureguide.codeplex.com) in the next refresh.

This weekend I did some explorations and testing in terms of the “Architecture tooling and modelling branching scenario” topic, to evaluate and confirm some of our discussions on architecture models, UML diagrams and the feasibility of branching and merging these artefacts.

My “simple” test:

1. Create a main branch
2. Drop a small solution with an empty UML Class diagram model project in main.
3. Branch main to Dev1 and Dev 2, simulating two development teams.
4. Do the unthinkable and add classes to the empty UML Class diagram model in both the Dev1 and Dev2 branch, using same class names and different operations.
5. Merge Dev1 back to main … everyone still happy.
6. Merge Dev2 back to main … pfffff … Houston we have a challenge.

I am probably lining myself up for a heated debate with the XML evangelists and enthusiasts, because my conclusion is to avoid branching and merging with models at all cost at this stage. The current tooling forces us into a challenging corner where we have to merge XML files, understand the related model file contents, contend with files that interleave other models, and cross link GUIDs and other metadata as shown in the following merge panes:

The challenging environment, however, seems to be a perfect out-of-band-Rangers solution opportunity :)

What are your thoughts and should we discourage development teams from branching and merging models?

One of the challenges you face in running a highly secure SQL Azure environment is too keep your connection string to SQL Azure secure. If you are running Windows Azure you need to provide this connection string to your Windows Azure code, however you might not want to provide the production database password to the development staff creating the Windows Azure package. In this series of blogs posts I will take about how to secure your SQL Azure connection string in the Windows Azure environment.

Scoping the Scenario

Without any security measures your connection string appears in plain text, and includes your login and password to your production database. The goal is to allow the code running on Windows Azure be able to read your connection string, however the developers making the package for Windows Azure deployment should not be able to read it. In order to do that, Windows Azure needs know the “secret” to unlock the connection string; however the developers that are making the package should not. How is this accomplished when they have access to all the files in the package?

Using the Windows Azure Certificate Store

The way that we have a secret that only Windows Azure “knows” is to pre-deploy a certificate to the Windows Azure Certificate Store. This certificate contains the private key of a public/private key pair. Windows Azure then uses this private key to decrypt an encrypted connection string that is deployed in the configuration files of the Windows Azure package. The public key is passed out to anyone needing to encrypt a connection string. Users with the public key can use it to encrypt the connection string, but it doesn’t allow them to read the encrypted connection string.

In this technique there are three different types of users:

1. The private key holder (the Windows Azure administrator) a very secure user that generates the private/public key pair, stores the private key backup, and puts the private key in place on Windows Azure. Only he and Windows Azure can decode the connection string.
2. The SQL Administrator, he knows the connection string and he uses the public key (gotten from the Windows Azure Administrator) to encoded the connection string. The encoded bytes are giving to the web developers for the web.config.
3. Web developers that make the Windows Azure package, they know the public key (everyone has access to it); however they don’t know the connection string nor the private key so they can’t get the SQL password.

Creating a Certificate

The first thing the Windows Azure administrator (private key holder) needs to do is use their local machine to create a certificate. In order to do this they will need Visual Studio 2008 or 2010 installed. The technique that I usually use to create a private/public key pair is with a program called makecert.exe.

Here are the steps to create a self-signed certificate in .pfx format.

1. Open a Visual Studio command prompt (Run as administrator), you will find the command prompt in the start menu under Visual Studio tools.
2. Execute this command:

   makecert -r -pe -n "CN=azureconfig" -sky exchange "azureconfig.cer" -sv "azureconfig.pvk"

   

3. You will be prompted for a password to secure the private key three times. Enter a password of your choice.

   

4. This will generate an azureconfig.cer (the public key certificate) and an azureconfig.pvk (the private key file) file.
5. Then enter the following command to create the .pfx file (this format is used to import the private key to Windows Azure). After the –pi switch, enter the password you chose.

   pvk2pfx -pvk "azureconfig.pvk" -spc "azureconfig.cer" -pfx "azureconfig.pfx" -pi password-entered-in-previous-step

6. You can verify that the certificate has been created by looking in the current directory in the Visual Studio command prompt.

   

Summary

In part two of the blog series I will show how the Windows Azure Administrator imports the private key (.pfx file) into Windows Azure. Do you have questions, concerns, comments? Post them below and we will try to address them.

This post is intended for those who are already familiar with SQL Server and want to get started working with SQL Azure.  One of the best ways to get up and running quickly is to migrate an existing SQL Server database to SQL Azure.  I chose the AdventureWorksDW2008R2 database because it’s optimized for building sample queries and reports.

It’s important to note before you begin that SQL Azure is a paid, subscription-based cloud service.   Subscriptions are billed based upon database edition (Web or Business), size, and the amount of data transferred in and out.  There are a variety of special offers available that significantly reduce the expense of getting started, such as the Windows Azure Platform MSDN Premium offer for MSDN subscribers.

So think through what you are doing in terms of the databases you create, editions, sizes and the amount of data you move in and out.

It’s also important to note that SQL Azure does not support all SQL Server data types and features. This can complicate the process of migrating your database.  Make sure you understand all of the Guidelines and Limitations before you get started.  

Initial Attempts

It’s worth noting that I tried a few approaches before I found something that worked, which I call the brute force approach.  Here’s a quick overview of some of my initial attempts.  Please note that at the time of this writing I was working with SQL Server 2008 R2 RTM tools and SQL Azure Service Update 4.

Copy Database Wizard

First I tried the Copy Database Wizard in SQL Server Management Studio, but it does does not yet support SQL Azure and failed with the error message:

Operation not supported on version 10.25. (Microsoft.SqlServer.SqlEnum)

Import and Export Wizard

My next attempt was to try the SQL Server Import and Export Wizard in SQL Server Management Studio.  This wizard generates a SQL Server Integration Services package that is capable of copying schema and data, but not other database objects like constraints and stored procedures.  Still, I wanted to see if it would work.  The Migrating Databases to SQL Azure topic in the online documentation documentation indicates that it does work, but every time I tried to connect I got the following error message:

Cannot get the supported data types from the database connection "Provider=SQLNCLI10;Data Source=myserver.database.windows.net;User ID=mysqladminuser@myserver;Auto Translate=false;Initial Catalog=AdventureWorksDW2008R2".

The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator. (Microsoft SQL Server Native Client 10.0)

At this point I was going to build my own custom Integration Services package, but I decided not to because I needed to migrate more than just schema and data.  I wanted to migrate all of the objects in the database as well.

SQL Azure Migration Wizard

There is a handy utility on CodePlex called the SQL Azure Migration Wizard (thanks to David Browne and Ashish Jaiman).  This tool does a great job of analyzing an existing database and generating scripts to create a compatible database in SQL Azure, then migrates the data.  While the scripts it generates are really useful, I found the tool itself was not very stable.  It crashed on me a couple of times.  

The most recent release at the time of this writing is 3.3.7 and was published on 3-Sep-2010.  There seems to be a lot of activity in this project so you can be sure that David and Ashish will continue to make improvements.

Brute Force Approach

After my initial attempts were unsuccessful, I resorted to what always works best for me and that’s the brute force approach.  Doing things this way gave me a much better understanding of the differences between SQL Server and SQL Azure, and now I have a nice library of routines I can use for future projects which I’ll share with you in this post.

Here’s an outline of the brute force approach.  More detail is provided in the sections that follow.

1. Provision the source SQL Server database
2. Provision the destination SQL Azure database
3. Generate a DDL script
4. Execute the DDL script against SQL Azure
5. Create migration assistant stored procedures
6. Disable foreign key constraints
7. Disable non-clustered indexes
8. Use bcp to export table data from your source SQL Server database
9. Use bcp to import table data into your destination SQL Azure database
10. Rebuild non-clustered indexes
11. Enable foreign key constraints

1. Provision the source SQL Server database

In this step you will install SQL Server 2008 R2 and the AdventureWorksDW2008R2 database.

1. Download and install SQL Server 2008 R2
2. Download and install the Sample Databases for Microsoft SQL Server 2008 R2.   Make sure to install the AdventureWorksDW2008R2 database.  This will create all of the necessary database objects and load a bunch of sample data (about 75 MB worth).

2. Provision the destination SQL Azure database

In this step you will provision an empty SQL Azure database that you will use to migrate all of the AdventureWorksDW2008R2 database objects contained in your local SQL Server instance.

1. Make sure you have a Windows Live ID set up.  You will need it to sign up for SQL Azure.
2. Review the Windows Azure Platform Options and purchase the right one for your needs.  Since I’m an MSDN Premium subscriber, I took advantage of the Windows Azure Platform MSDN Premium offer.
3. Create and activate your SQL Azure subscription.  You will be asked to create an Administrator Username and password and choose a location where your server will be hosted.  Make a note of the password you select.
   
   Tip: Avoid using special characters like “@” in your password.  Stick with alphanumeric characters and hyphens.  Some database utilities like bcp (bulk copy program) may have problems encoding special characters in a password.
4. Sign into the Windows Azure Developer Portal, click on the SQL Azure tab and select the Project Name associated with the SQL Azure subscription you just activated.
5. Make a note of the information in the Server Information section, including:
   Server Name (e.g. myserver.database.windows.net)
   Administrative Username  (e.g. mysqladminuser)
6. In the Databases tab, click on Create Database, and enter the following information:
   Name of your database: AdventureWorksDW2008R2
   Specify an edition: Web
   Specify the max size: 1 GB
   
   Tip: Right now the main difference between Web and Business database editions is storage and pricing.  Web edition databases can be provisioned for up to 5 GB of relational storage.  Business edition databases can be provisioned for up to 50 GB of relational storage.  Web edition is significantly less expensive for paid subscriptions.  As SQL Azure evolves, “enterprise” features will most likely be monetized by requiring Business edition.
7. Click Create
8. In the Firewall Settings tab, check the “Allow Microsoft Services access to this server” option.  This will allow other services running in the Azure Services environment to interoperate with your SQL Azure server.
9. In the Firewall Settings tab, click the Add Rule button, and enter the correct IP address range to grant access to the IP addresses you will use to connect to SQL Azure, for example:
   Name: GrantAccessToAllAddresses
   IP Range: 0.0.0.0 to 255.255.255.255
   
   Tip: The example shown here grants access to all IP addresses.  Grant access only to the IP addresses you actually need to avoid unauthorized usage..

3. Generate a DDL script

In this step you will generate a DDL script capable of recreating all of the objects in your source database.  DDL stands for “Data Definition Language” which is shorthand for the various Transact-SQL commands used to create database objects such as tables, views and stored procedures.

1. Launch SQL Server Management Studio.
2. Connect to the SQL Server instance that you installed the AdventureWorksDW2008R2 database on.
3. Expand the Databases node in Object Explorer, right-click on AdventureWorksDW2008R2 and select Tasks > Generate Scripts.
4. In the Choose Objects dialog, choose the “Select Specific Database Objects” option, then check the Tables, Views, Stored Procedures and User-Defined Functions options.
   
   Tip: AdventureWorksDW2008R2 contains a DDL Trigger.  SQL Azure does not currently support DDL Triggers so do not select this option.
5. Expand the Tables node and uncheck the following tables:
   
   1. AdventureWorksDWBuildVersion
   2. DatabaseLog
   3. FactFinance
   
   Tip: SQL Azure requires all tables to have a clustered index.  These tables do not have clustered indexes, and they are not essential for this particular sample database.
   
6. In the Choose Objects dialog, click Next.
7. In the Set Scripting Options dialog, click the Advanced button and make the following changes, the click OK:
   1. Set the General > “Script for the database engine type” option to “SQL Azure Database”
   2. Set the Table/View Options > Script Indexes option to True
8. In the Set Scripting Options dialog, set the output type to “Save scripts to a specific location”, and choose the “Save to new query window” option, then click Next.  
9. Review the information in the Summary dialog, then click Next. At this point the wizard will interrogate the schema of the source database and generate a script  to rebuild all of the objects in the database into a new query window.
10. Review the information in the Save or Publish Scripts dialog then click Finish.
11. Return to SQL Server Management Studio and review the script that was generated.

4. Execute the DDL script against SQL Azure

In this step you will execute the DDL Script you generate against the AdventureWorksDW2008R2 database you provisioned in SQL Azure.  Once completed, all of the tables, views, stored procedures and other objects from your source database will exist in your newly provisioned SQL Azure database.  At this point there will be no data in the tables.

1. Right-click in the query window and select Connection > Change Connection.  This will bring up the Connect to Database Engine dialog so you can connect to your newly created AdventureWorksDW2008R2 database in SQL Azure.  Enter the connection information you noted earlier, for example:
   Server name: myserver.database.windows.net
   Authentication: SQL Server Authentication
   Login: mysqladminuser@myserver
   Password: mysqladminuserpassword
   
   Tip: You can select the Remember Password option to avoid having to retype your password each time you connect.
2. Click Connect.
3. Change the active database to AdventureWorksDW2008R2 using theh Available Databases drop-down list box in the tool bar.
   
   Tip: Always check your current database context before running a script to avoid making changes to the wrong database.
4. Execute the query by pressing F5 or by selecting the Query > Execute menu option.  
5. Review the status information at the bottom of the query window and verify that the query executed successfully. 
6. Using Object Explorer, connect to your SQL Azure server using the appropriate credentials.  Expand the Databases node, then expand the Tables node.  Review the tables that were created and compare them to those in your local SQL Server instance.

5. Create migration assistant stored procedures

In this step you will create two stored procedures in the SQL Azure AdventureWorksDW2008R2 database that will simplify the process of migrating your data. 

The SetForeignKeyEnabledStatus stored procedure will be used to disable foreign key constraints during data migration.  This will permit you to load your tables in whatever order is convenient without regard to primary key / foreign key relationships.  You will run this stored procedure again when data migration is complete to re-enable all of the foreign key constraints.

The SetIndexEnabledStatus stored procedure will be used to disable all non-clustered indexes during data migration.  This speeds up the data loading process.  You will run this stored procedure again when data migration is complete to rebuild all of the non-clustered indexes.

Use the following procedure to create the stored procedures.  The source code for the CreateMigrationAssistantProcedures.sql Transact-SQL script file referenced in the instructions is included at the end of this section.  To execute the script, you will use the sqlcmd utility, which is a command-prompt utility useful for performing batch operations against SQL Server and SQL Azure.

1. Copy the source code for the CreateMigrationAssitantProcedures.sql script file into notepad and save it in a convenient folder.
2. Open a command prompt and change the current directory to the folder in step 1.
3. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   sqlcmd -S myserver.database.windows.net -U mysqladminuser@myserver -P mysqladminuserpassword -d AdventureWorksDW2008R2 -i CreateMigrationAssistantProcedures.sql –b
   
   Tip: The –b parameter ensures that sqlcmd will return a non-zero error code if an error occurs when running a script.  This can be used to terminate a batch file if an error occurs.
   
4. Launch SQL Server Management Studio, connect to your SQL Azure server, and expand the Databases > AdventureWorksDW2008R2 > Programmability > Stored Procedures node.  Verify that the SetForeignKeyEnabledStatus and SetIndexEnabledStatus stored procedures are in the list.  

Here’s the source code for the CreateMigrationAssistantProcedures.sql script referenced above:

IF OBJECT_ID('[dbo].[SetForeignKeyEnabledStatus]','P') IS NOT NULL
    DROP PROCEDURE [dbo].[SetForeignKeyEnabledStatus];
GO

CREATE PROCEDURE [dbo].[SetForeignKeyEnabledStatus]
(
    @enabled bit
)
AS
BEGIN
    DECLARE
        @schema_name sysname,
        @table_name sysname,
        @fk_constraint_name sysname,
        @cmd_txt varchar(8000);

    DECLARE fk_cursor CURSOR FOR
        SELECT
            sc.name AS schema_name,
            so.name AS table_name,
            so2.name AS fk_constraint_name
        FROM
            sys.objects so
            inner join sys.schemas sc ON so.schema_id = sc.schema_id
            inner join sys.foreign_key_columns fk ON so.object_id = fk.parent_object_id
            inner join sys.objects so2 ON so2.object_id = fk.constraint_object_id
        WHERE
            so.type = 'U';

    OPEN fk_cursor;

    FETCH NEXT FROM fk_cursor INTO
        @schema_name,
        @table_name,
        @fk_constraint_name;

    WHILE @@FETCH_STATUS = 0
    BEGIN
        IF @enabled = 0
            SET @cmd_txt = 'ALTER TABLE [' + @schema_name + '].[' + @table_name + '] NOCHECK CONSTRAINT [' + @fk_constraint_name + '];'
        ELSE
            SET @cmd_txt = 'ALTER TABLE [' + @schema_name + '].[' + @table_name + '] WITH CHECK CHECK CONSTRAINT [' + @fk_constraint_name + '];';                    
        PRINT @cmd_txt;
        EXECUTE (@cmd_txt);
        FETCH NEXT FROM fk_cursor INTO
            @schema_name,
            @table_name,
            @fk_constraint_name;
    END;

    CLOSE fk_cursor;
    DEALLOCATE fk_cursor;
END;
GO

IF OBJECT_ID('[dbo].[SetIndexEnabledStatus]','P') IS NOT NULL
    DROP PROCEDURE [dbo].[SetIndexEnabledStatus];
GO

CREATE PROCEDURE [dbo].[SetIndexEnabledStatus]
(
    @enabled bit
)
AS
BEGIN
    DECLARE
        @schema_name sysname,
        @table_name sysname,
        @index_name sysname,
        @cmd_txt varchar(8000);

    DECLARE idx_cursor CURSOR FOR
        SELECT
            sc.name AS schema_name,
            so.name AS table_name,
            si.name AS index_name
        FROM
            sys.objects so
            inner join sys.schemas sc ON so.schema_id = sc.schema_id
            inner join sys.indexes si ON so.object_id = si.object_id
        WHERE
            so.type = 'U'
            AND si.index_id > 1;
    OPEN idx_cursor;

    FETCH NEXT FROM idx_cursor INTO
        @schema_name,
        @table_name,
        @index_name;

    WHILE @@FETCH_STATUS = 0
    BEGIN
        IF @enabled = 0       
            SET @cmd_txt = 'ALTER INDEX [' + @index_name + '] ON [' + @schema_name + '].[' + @table_name + '] DISABLE;'
        ELSE
            SET @cmd_txt = 'ALTER INDEX [' + @index_name + '] ON [' + @schema_name + '].[' + @table_name + '] REBUILD;'
        PRINT @cmd_txt;
        EXECUTE (@cmd_txt);
        FETCH NEXT FROM idx_cursor INTO
            @schema_name,
            @table_name,
            @index_name;
    END;

    CLOSE idx_cursor;
    DEALLOCATE idx_cursor;
END;
GO

These two stored procedures iterate through objects (foreign keys and indexes) in system catalog views.  For each iteration I dynamically construct a Transact-SQL command to enable or disable the object, then execute the dynamically constructed command.  I hope you find them useful.

6. Disable foreign key constraints

In this step you will use the SetForeignKeyEnabledStatus stored procedure created in the previous step to disable all of the foreign key constraints in the AdventureWorksDW2008R2 SQL Azure database.  This will make it easier to load data by removing the need to do it in a specific order to avoid violating foreign key constraints.  We will re-enable the foreign key constraints later after you are finished loading your data.

1. Open a command prompt.
2. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   sqlcmd -S myserver.database.windows.net -U mysqladminuser@myserver -P mysqladminuserpassword -d AdventureWorksDW2008R2 -Q "EXECUTE [dbo].[SetForeignKeyEnabledStatus] 0" –b
   
   Tip: Use the –Q parameter to send a single command instead of executing a script file.
   

7. Disable non-clustered indexes

In this step you will use the SetIndexEnabledStatus stored procedure created previously to disable all of the non-clustered indexes in the AdventureWorksDW2008R2 SQL Azure database.  This will improve the performance of data loading by avoiding incremental index rebuilds during the loading process.  We wil lre-build the non-clustered indexes later after you are finished loading your data.  Note that we will not disable clustered indexes since the data be loaded in clustered index order, and SQL Azure requires clustered indexes on all tables.

1. Open a command prompt.
2. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   sqlcmd -S myserver.database.windows.net -U mysqladminuser@myserver -P mysqladminuserpassword -d AdventureWorksDW2008R2 -Q "EXECUTE [dbo].[SetIndexEnabledStatus] 0" –b
   

8. Use bcp to export table data from your source SQL Server database

In this step you will use the bcp (bulk copy program) command-line utility to export data from your source SQL Server database.  This step will need to be done once for each table in the AdventureWorksDW2008R2 database (with the exception of the three tables we excluded in step 3).  When you complete this step, you should have one “native” file for each of the tables.

1. Open a command prompt.
2. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   bcp dbo.MyTableName out MyTableName.dat -n -S MySqlServerName –T
   
   Tip: Use the –n parameter to use the “native” file format for export.   The native format improves performance on import by avoiding unnecessary conversions.
   
   Tip: Use the –T parameter to connect to SQL Server using your Windows credentials.
   
3. Examine the output and verify that the file was created.

9. Use bcp to import table data into your destination SQL Azure database

In this step you will use the bcp command-line utility to import data from a “native” file into your destination SQL Azure data base.  This step will need to be done once for each table in the AdventureWorkdsDW2008R2 database (with the exception of the three tables we excluded in step 3).  When you complete this step, all of your data should be loaded.

1. Open a command prompt.
2. Set the current directory to the folder that contains the files created in step 8.
3. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   bcp dbo.MyTableName in MyTableName.dat -n -S myserver.database.windows.net -Umysqladminuser@myserver -Pmysqladminuserpassword -E
   
   Tip: Bcp is very picky about parameter formats.  Do not use a space after the –U and –P parameters.
   
   Tip: Be careful when importing data into columns that use the IDENTITY property.   Use the –E parameter to use values in the data file for IDENTITY columns instead of generating new identity values during import.  If you don’t do this you risk breaking foreign key relationships.
   
4. Examine the output to ensure that all data was successfully copied into the destination table.

10. Rebuild non-clustered indexes

In this step you will use the SetIndexEnabledStatus stored procedure to rebuild the non-clustered indexes you disabled in step 7.  It’s best to do this in one shot after loading all of your data.

1. Open a command prompt.
2. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   sqlcmd -S myserver.database.windows.net -U mysqladminuser@myserver -P mysqladminuserpassword -d AdventureWorksDW2008R2 -Q "EXECUTE [dbo].[SetIndexEnabledStatus] 1" –b
   

11. Enable foreign key constraints

In this step you will use the SetForeignKeyEnabledStatus stored procedure to enable the foreign key constraints you disabled in step 6.

1. Open a command prompt.
2. Execute the following command using the appropriate connection details for your SQL Azure server:
   
   sqlcmd -S myserver.database.windows.net -U mysqladminuser@myserver -P mysqladminuserpassword -d AdventureWorksDW2008R2 -Q "EXECUTE [dbo].[SetForeignKeyEnabledStatus] 1" –b
   

Putting it all together

Now that you know how to do each of the steps, here’s a handy batch file called bcp.adventureworksdw2008r2.cmd you can use to automate all of the operations performed in steps 5-11.  The only other file you will need to run this batch is the CreateMigrationAssitantProcedures.sql script file you created in step 5. 

@ECHO OFF

SET SourceSqlServerName=localhost
SET DestSqlServerName=myserver.database.windows.net
SET DestSqlUserName=mysqladminuser@myserver
SET DestSqlUserPassword=mysqladminuserpassword
SET SqlDbName=AdventureWorksDW2008R2

ECHO ******************************
ECHO Creating Migration Assistant Procedures
ECHO ******************************

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -i CreateMigrationAssistantProcedures.sql -b
IF ERRORLEVEL 1 GOTO ABORT

ECHO ******************************
ECHO Disabling Foreign Key Constraints
ECHO ******************************

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "EXECUTE [dbo].[SetForeignKeyEnabledStatus] 0" -b
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.AdventureWorksDWBuildVersion

ECHO ******************************
ECHO Disabling Nonclustered Indexes
ECHO ******************************

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "EXECUTE [dbo].[SetIndexEnabledStatus] 0" -b
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimAccount

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword% -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimCurrency

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword% -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimCustomer

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimDate

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimDepartmentGroup

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimEmployee

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimGeography

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimOrganization

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimProduct

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimProductCategory

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimProductSubCategory

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimPromotion

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimReseller

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimSalesReason

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimSalesTerritory

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.DimScenario

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactAdditionalInternationalProductDescription

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactCallCenter

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactCurrencyRate

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword% -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactInternetSales

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactInternetSalesReason

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactResellerSales

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactSalesQuota

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.FactSurveyResponse

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

SET TableName=dbo.ProspectiveBuyer

ECHO ******************************
ECHO Migrating data for %TableName%
ECHO ******************************

bcp %SqlDbName%.%TableName% out %TableName%.dat -n -S %SourceSqlServerName% -T

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "DELETE %TableName%;" -b

bcp %SqlDbName%.%TableName% in %TableName%.dat -n -S %DestSqlServerName% -U%DestSqlUserName% -P%DestSqlUserPassword%  -E

if exist %TableName%.dat DEL %TableName%.dat
IF ERRORLEVEL 1 GOTO ABORT

ECHO ******************************
ECHO Enabling Nonclustered Indexes
ECHO ******************************

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "EXECUTE [dbo].[SetIndexEnabledStatus] 1" -b

SET TableName=dbo.AdventureWorksDWBuildVersion
IF ERRORLEVEL 1 GOTO ABORT

ECHO ******************************
ECHO Enabling Foreign Key Constraints
ECHO ******************************

sqlcmd -S %DestSqlServerName% -U %DestSqlUserName% -P %DestSqlUserPassword% -d %SqlDbName% -Q "EXECUTE [dbo].[SetForeignKeyEnabledStatus] 1" -b
IF ERRORLEVEL 1 GOTO ABORT
GOTO ENDBATCH

:ABORT

ECHO !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ECHO Batch aborted due to error condition
ECHO !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

GOTO ENDBATCH

:ENDBATCH
ECHO !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ECHO Batch execution completed
ECHO !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

You may see this behaviour when accessing an SSL enabled Website through IE 6.0 after installing MS10-049.

“The Page cannot be displayed”

This can happen for websites that use TLS security protocol for encryption.

If you are experiencing this behaviour please check the following support KB for more information.

http://support.microsoft.com/kb/2384778

As you may recall from my Microsoft Partner logo, branding, naming updates revealed at WPC10 post, come October when the Microsoft Partner Network is fully launched, Microsoft partners will earn levels at the competency level, not the organization level.  In the past, there have been “Microsoft Gold Certified Partners” or “Microsoft Certified Partners” at an organization level.  Moving forward, organizations will be Microsoft Partners at the organization level and they will earn Silver level and Gold level for individual competencies (and yes, you can earn multiple competencies and mix and match Silver and Gold level competencies) to better help partners distinguish and differentiate their unique skills and areas of expertise for existing and prospective clients. 

For example:

In the past:	After Microsoft Partner Network launch:
“Certified” designation at organization level	“Silver” designation at competency level (“Business Intelligence” in this example)

For those of you looking to renew your membership in the Microsoft Partner Network with a Silver competency level, I am posting up this Step-By-Step guidance on how to go about doing this in order to help make the process as easy to follow for you as possible.

1. Build your plan: Use the Transition Tool (See my Microsoft Partner Network Transition Tool post for step by step guidance on using this tool) to identify the actions you need to gain new Silver competencies. (If you are unclear what competencies are best for your business, visit the Microsoft Partner Network Advantage as your first step.)
   • You will need your Organization Identification Number to use the Transition Tool. You can obtain this by logging into your account in Partner Membership Center.
2. If you need qualifying exams, advanced certifications or product tests, use the following:
   • Partner Portal Competency Requirements pages for links to exams, course prep and product tests
   • Exam Voucher Offers to get up to 30% off the cost of exams
   • Click to Chat with an expert regarding specific exam questions
3. If you need assessments go to the Business Assessment Requirements page to prepare and take the required Licensing and Sales and Marketing assessments
4. If you need Customer References, login to Partner Membership Center, click the Requirements and Assets dropdown and click “Create Customer References”
   

   - Click on the image to the right to see full size.  This shows you where the “Create Customer References” link is located.

5. Click here to complete the re-enrollment process and pay the Silver Competency fee

One note from a timing perspective, we are talking about your re-enrollment in the Microsoft Partner Network here, which means that the date that you will need to meet the requirements for the Silver level competencies by will be your anniversary date in the Microsoft Partner Network, not the initial launch date of the Microsoft Partner Network.  So if your anniversary date is January 31, 2011, then you have until then to meet the requirements at the Silver competency levels that you wish to achieve.

For those of you looking to achieve a Gold level competency in the Microsoft Partner Network, you may want to take a look at my: Gold Competency Step-by-step Checklist to Re-enrollment in Microsoft Partner Network post.

I hope this step-by-step guide helps you in your process to re-enroll in the Microsoft Partner Network at the Silver competency level.

Thank you and have a wonderful day,

Eric Ligman – Follow me on TWITTER, LinkedIn, and RSS and see “What I’m thinking”
Global Partner Experience Lead
Microsoft Worldwide Partner Group
This posting is provided "AS IS" with no warranties, and confers no rights

 

На странице http://msdn.microsoft.com/ru-ru/magazine/default.aspx опубликован перевод июньского номера журнала MSDN Magazine. 

Основные материалы номера:

• Silverlight в мире непостоянного подключения
• AppFabric: Практическое использование и интеграция
• SOA: Решение проблемы узких мест масштабирования с помощью распределенного кэширования
• Профилирование одновременного выполнения на предмет конфликтов за ресурсы в Visual Studio 2010
• Возьмите под контроль ведение журнала и трассировку в Windows Azure
• Кодируйте свои видео, используя пакет SDK кодировщика Microsoft Expression Encoder 3
• Обеспечение выполнения комплексных правил бизнес-данных с помощью WPF
• Создание функционально насыщенных интернет-приложений с помощью протокола Open Data