Category | SQL

I have added a this special page to my blog to discuss with users how I build out my SharePoint 2010 (and 2007) labs.  Many people ask me on a regular basis what I use for development, what software do I use, and even what hardware I have running so I thought this post would be useful.    Furthermore, I’ve made it a prerequisite for those that work for me to build their own lab because there’s no better experience than hands on experience (not to mention it weeds out the individuals that simply cannot cut it).  Hardware Currently I have 2 workstations that I use as lab machines...

---

http://www.sharepointassist.com/2010/02/04/sharepoint-2010-installation-part-1-server-build/ http://www.sharepointassist.com/2010/02/10/sharepoint-2010-installation-part-2-install-sql/ http://www.sharepointassist.com/2010/02/11/sharepoint-2010-installation-part-3-install-sharepoint/ (YOU ARE HERE) This article is part 3 in a 4 part series that shows how I build my SharePoint 2010 development environment from the ground up.  In the previous series I built a Windows 2008 R2, configured the Active Directory Domain Services role, provisioned SharePoint service accounts, configured the IIS role,...

---

http://www.sharepointassist.com/2010/02/04/sharepoint-2010-installation-part-1-server-build/ http://www.sharepointassist.com/2010/02/10/sharepoint-2010-installation-part-2-install-sql/ (YOU ARE HERE) http://www.sharepointassist.com/2010/02/11/sharepoint-2010-installation-part-3-install-sharepoint/ This article describes the installation process for a SQL server on an all-in-one SharePoint 2010 development server. If you didn't follow Part 1 of the SharePoint 2010 Installation series you'll need to create a SQL service account to support the SQL Server 2008.  While there are many...

---

A SQL Server alias is a tidy way to protect yourself from configuration changes in a SharePoint farm. Anybody who works with SharePoint on a regular basis knows that it is very difficult to move SharePoint to a different SQL Server. When disaster strikes wouldn't it be nice if you could simply change SQL Server that SharePoint references? To do so, install the SQL client access tools on each server and create a SQL Alias in SQL Server Configuration Manager, from there your SharePoint Server can be re-homed with little effort. Note, there are two methods to create a SQL Server alias, one for machines...

---

Problem SQL Server has a broken reference somewhere preventing you from deleting a maintenance job, presumably a job that you created as a maintenance plan. OR (worse yet SQL claims that it isn't "aware" of this job) Solution So the ultimate solution to this problem is to delete the job and all of its references/dependencies/children using a stored procedure (don't worry, I provided the stored procedure below). Step 1 Backup your msdb database. Step 2 Select the sysjobs from the msdb database and copy the job_id of the plan in question. Match up the name of the job with the item...

---