PowerApps RAW!

Open a query window in the Microsoft SQL Server Management Studio and run the following command.  It will display to you the current name of the SQL server. sp_helpserver GO Next we will run the following commands.  Replace old_name with the SQL server name you discovered in the sp_helpserver command, and replace new_name with the name of the server.  (include the single quotes our the names) sp_dropserver 'old_name' GO sp_addserver 'new_name', local GO Open the SQL Server Configuration Manager and resart the SQL Services. To deteremine if the update was successful run the following command against the 'master' database.  If the query displays the new_name you assigned to SQL it will be displayed here.  If there is nothing displayed then something went wrong. SELECT @@SERVERNAME

Hey Everybody, Just wanted to let you know that my wonderful Wife, Anne Marie, is going to be performing in Bye Bye Birdie with the Arlington Players. She has a lead role in the production as the character of Rosie Alvarez and has several major song and dance numbers. I would love if you could all make it out. Performance dates and ticket information is below. Bye Bye Birdie Performance dates: September 18, 19, 20(m), 25, 26, 27(m), October 2 & 3, 2009 Click here to purchase your tickets online.

One of the things I do when setting up a CRM 4.0 server is modify the Recovery settings of the Asynch process. This process tends to have a lot of difficulty recovering if it loses the connection to SQL. Figure 1 By default the service is set to Restart only on the first failure and the restart time is set to occur after 1 minute (Figure 1). The problem is that it typicaly takes a SQL server longer than one minute to reboot. In order to better ensure that you don't need to restart the service manually I typicaly change the Second failure to Restart the Service and set the Restart service after setting to something between 3 and 5 minutes (Figure 2). Figure 2 By tweeking these setting you can help reduce the strain on your support folks by not always having to do a manual restart of this service every time they want to install patches on the SQL box.  Also your users won't be sitting there wondering why their workflows are not kicking off.

So here was my issue. I needed to copy some <binary data> from one row in a table to another row. I tried using the SQL Server Managment Studio but it does not allow you to copy and past binary information. Instead I used a UPDATE... FROM SQL statement. Here is an example: UPDATE LoadTestRun SET LoadTest = b. LoadTest FROM LoadTestRun, LoadTestRun b WHERE LoadTestRun.LoadTestRunID = 4 AND b.LoadTestRunID = 1 Here is the generic format: UPDATE table SET field = b.field FROM table, table b WHERE table.PirmaryKeyID = "Copy To ID" AND b.PrimaryKeyID = "Copy From ID"

Learned a very important lesson. If you don't set up a results repository database before running a load test in Visual Studio you won't be able to pull up your reports later. In this example only one machine was being used for load testing and SQL Express was installed as part of Visual Studio. To create the results repository database in SQL Express follow the instructions below. If you want additional information or want to know how to create the database in SQL Standard check out Microsoft's instructions at http://msdn.microsoft.com/en-us/library/ms182600.aspx -Open a command prompt by going to Start -> Run and type in CMD and hit Enter -Type: cd n:\Program Files\Microsoft Visual Studio 9\Common7\IDE -Type: SQLCMD /S localhost\sqlexpress /i loadtestresultsrepository.sql

I was recently tasked with migrating a secondary site collection to a new SharePoint server and making it the primary site collection. Here is an example of what a URL looks for for a secondary site collection. http://www.example.com/sites/collection Here is an example of what a URL looks like for a root site collection: http://www.example.com/ You will notices that secondary site collection are placed by default under /sites/ Completing the Migration: 1. Run a backup of the site collection on the original server using STSADM. Here is the command line I used: stsadm -o backup -filename "c:\backups\backup.bak" -url http://www.example.com/sites/collection 2. Copy the backup file to the new server where a new SharePoint instance is created and contains a new root site collection. 3. Run a restore of the site collection on the new server using STSADM. Here is the command line I used. stsadm -o restore -filename "c:\restores\backup.bak" -url http://w...

Bad Idea... Changing the password of the SharePoint service account used to set up and run everything SharePoint. If you have done this read the next paragraph before touching your keyboard again. Worse Idea... Trying to change the password back to what it was, but when confronted with domain password policies that do not allow you to change the password to one you have used recently you delete the user. Then you go in and recreate the user and assign him the old password. IMPORTANT : If you go into the Active Directory Users and Computers under the Administrator tools and you are a domain administrator you can reset the password of any user to whatever you want. Domain policies be damned. So if you have not deleted the service account yet just change the password in the way I just described. Then reset your sharepoint machine and be thankful that you don't have to read the rest of this article. Now lets say you decided to do these two things..... ughhhh. Why doesn't recr...