Copy the public key and add it to the GIT space we created at Assembla.
Right click a folder on your local system and create a Git repository.
Right click the local Git repository folder, TortoiseGit >> Settings >> Git >> Remote Name: Name of project URL: Assembla PUSH URL under the project Putty: Load the private key you exported earlier
Finally, create the “master” branch for the first time, by right clicking on the Git repository folder and clicking “Git Commit –> master""
Entitle the message “initial” and check the “Select / Deselect All” box, click “Ok”
Download SkyDrive Simple Viewer – which, very simply, lists the URLs associated with your SkyDrive account (screenshot below)
Right click “My Computer”, click “Map network drive”, choose a drive letter, paste a URL returned from DumpUrls.exe into the “Folder” text box and click “Finish”
Provide your Windows Live ID username and password.
It appears, when provisioning VMKernels, on different VLANs, with Dell switches, the port the VMKernel is plugged requires “Tagged” as the VLAN Membership option. VM Port Groups can remain “Untagged”
The easiest way to do this is a table level script.
function InsertRecord()
{
var sql = ‘SELECT comp_idcust FROM vCompany WITH (NOLOCK) WHERE comp_companyid=’ + Values(’oppo_primarycompanyid’);
var companyRecord = eWare.CreateQueryObj(sql);
companyRecord.SelectSql();
Values(’oppo_primarycompany_idcust’) = companyRecord.FieldValue(’comp_idcust’);
}
function PostInsertRecord()
{
// Handle post insert record actions here
}
function UpdateRecord()
{
var sql = ‘SELECT comp_idcust FROM vCompany WITH (NOLOCK) JOIN vOpportunity ON oppo_primarycompanyid = comp_companyid WHERE ‘ + WhereClause;
var companyRecord = eWare.CreateQueryObj(sql);
companyRecord.SelectSql();
Values(’oppo_primarycompany_idcust’) = companyRecord.FieldValue(’comp_idcust’);
}
Unfortunately, SQL 2005 is unable to restore .BAK files created by SQL 2008. Subsequently, SQL 2005 is unable to attach MDF and LDF files created by SQL 2008.
Here are the steps to copy a SQL 2008 database to SQL 2005.
From SQL 2008, right click on the database, click Tasks >> Generate Scripts
The “Generate and Publish Scripts” wizard is displayed. Click Next
Take the default, which should be, “Script entire database and all database objects”. Unless of course, you don’t want the whole database. In this case you can select tables, views, etc.
For the export options, make sure “Save to file” is selected. Additionally, give a unique name for the generated sql file. In this example, we are exporting the SAMINC database, so we have titled the sql export file, saminc.sql.
Almost there! Click “Advanced”
From the “Advanced Scripting Options” make two changes. Change “SQL for Server Version” to “SQL Server 2005” and change “Types of data to script” to “Schema and data”.
Click “OK” to close the “Advanced Scripting Options” and click “Next”.
After the wizard finishes, copy the resulting sql file to the SQL 2005 server.
Open SQL Management Studio. From within SQL Management Studio, click File >> Open and select the resulting sql file.
IMPORTANT!!! Finally, change the directory to the correct data directory.
