Replaced Fuel Filter on the Ford F-150

Since I got the truck back in business, I’ve been driving it regularly. Over the last two weeks I noticed the vehicle seemed to have a hard time getting fuel. I suspected an issue with the fuel supply but wasn’t 100% sure. Every now and then when I came to a stop the truck seemed like it wanted to stall. As I continued to drive, every now and then it seemed like it was not getting the fuel despite the fact I did not let up on the gas pedal.

I did some research on google and a lot of threads recommended changing the fuel filter. I did additional searches to get an idea of how to replace the filter and could not believe how easy it is to access and replace. The local repair shop quoted me about $75 to replace it. I bought the part at AutoZone for $9.74 which is a savings of $65.26 had I taken it to the shop.

After everything was all said and done the test drive was very smooth. There was no sense of stalling when I came to a stop and as I was driving I did not feel any hesitation. The best part is that the truck starts up right away and I no longer need to keep my foot on the gas pedal to keep it running to warm it up. All this time I thought it was just an issue with the engine being cold. You live and learn!


Replaced the alternator in my 1990 Ford F-150

1990 Ford F-150

I’ve had this 1990 Ford F-150 since April 2014 and I’ve known there was an issue with either the battery, alternator or there was a parasitic draw that would kill the battery within 18-24 hours. I haven’t had the time to really look into it until now. I’ve done some research to get a few ideas of what to check for. I had a hunch it was the alternator after I replaced the battery and the next morning it wouldn’t even crank.

The reason that sparked this adventure was that my 2007 Nissan Frontier wouldn’t start either. I figured since I needed to head over to Auto Zone, I better make good use of my time and kill two birds with one trip. I took both batteries over and they tested them both. The battery from my Nissan turned out to be bad but the Ford’s test results were positive, so I left the battery with them overnight to fully charge it.

The afternoon of (Super Bowl XLIX) I mustered up the energy to tackle the alternator. Mind you, I am no mechanic but I managed to remove the alternator with ease. Of course I took a lot of photos to document the connections, bolts, etc… to make sure things go back the way they were removed. I also documented the socket sizes to remove the guess-work for the next time I have to perform this task. The tension and bottom bolt for the alternator used a 5/8 socket and the top bolt for the alternator used a 9/16 socket. Then there was the 8 socket for the battery brace.

The entire process including the removal of the alternator, the trip to Auto Zone to pick up the battery (left overnight to charge), purchasing and installing the new alternator took less than an hour. It cost me a grand total of $95.29 just for the part. I got a quote from a few local auto shops and it would have cost me around $375 – $440. So I saved myself around $279 – $344. A little elbow grease, a little research mixed with willingness and a can-do attitude equals big savings.


Goodbye Stored Procedures… Hello Maintenance Plans

I like to write my our procedures for the sheer fact that I like the control. Which means I had sprocs that cleared out the history logs retaining only the records within the last 90 days. I also had sprocs that performed system and user database backups which would backup to a network share and append my timestamp (i.e. master_YYYYMMDD_HHMM.bak) which were all executed by agent jobs. Depending on the need I would setup Full, differential and log backups; furthermore, my process would also purge old back up files.

'_' +
+ '_' +
+ '.bak'

I am here to say I have given up my ways and have been walking a different path. I moved away from my custom methods and adopted Maintenance Plans. I use them for backing up the system and user databases if the system is not being serviced by a backup system as well as running DBCC CHECKDB against each database. I also use maintenance plans to purge the history logs that falls outside of a 90 day threshold and perform reorgs or rebuilds of my indexes. For a complete task list visit: Maintenance Tasks.

I am kidding, it’s hard to break away from writing my own procedures. Maintenance Plans are good if you’re getting started with SQL Server and really don’t understand the fundamentals of writing your own queries to accomplish the same outcome. I don’t know if this makes me a control freak or not. Oh wait I said that in the beginning of this post. Anyhow if you want to setup maintenance plans here is what you need to do.

One thing to know before we jump in is that you need to grant the SQL Agent Service account write access to the backup share in my case the Agent service is “sqlservice”. Typically you would use a domain account (i.e. domain\sqlservice) which you will need to grant Change access on the directory where you will be storing the backups (i.e. \\server\backups\).

If you are using the default file path which was set during the initial install of SQL Server then the path would be like <drive letter>:\..\MSSQL10_50.<instance name>\MSSQL\Backup\ and will be using the SQLServerMSSQLUser$<computer name>$<instance name> which has enough permissions.

Also you need know Maintenance Plans and the SQL Agent are not features you will find in Express editions. Well technically the SQL Agent is there, but it cannot be used/started in Express edition, so hopefully you have at the very least developer edition.

Now that I touched on a few reasons on why to use Maintenance Plans let’s kick our heels up and dig right in. You’ll need to be a sysadmin in order to create a maint plan so if you’re not then the following steps will be more informational than anything. If you have worked with SQL Server Integration Services then the Maintenance Plans design surface will look a bit familiar.

For this post we will be using two tasks: Backup Database and Maintenance Cleanup to schedule routine backups of the system database: (master, model and msdb). Once you run through this process creating another Maintenance Plan to address the user databases is extremely similar with literally one item to change. You’ll see what I am talking about in a moment. Let’s being…

Creating a Maintenance Plan for daily backups of System Databases

Step 1: Open up Management Studio, connect to your instance and expand Management
Step 2: Right click on Maintenance Plans and select New Maintenance Plan…
Step 3: Enter a specific name: (i.e. Daily_System_DB_Full_Backup) & click OK

If you are going to schedule a FULL backup let’s say on Sunday then the name of the Maintenance Plan would be along the lines of (i.e. Weekly_System_DB_Full_Backup). Then if you were going to incorporate daily differentials you might consider calling the Maintenance Plan: (i.e. Daily_System_DB_Diff_Backup). Perhaps you want to perform Full backups of the DBs daily and then perform Transaction Log backups hourly or every four hours, etc… you would want to make the names meaningful to the types of backups the Maintenance Plan is performing. Enough harping on that… I am beginning to hear crickets at his point.

Once you have clicked OK you arrive at the design surface where you will build your workflow process. The default is always Subplan_1 which you can leave or you can change the name. If your Maintenance Plan only utilizes a single subplan then the naming really doesn’t matter, but if you add additional subplans then you might want to consider naming them accordingly to better identify their purpose or intent as opposed to having Subplan_2, 3, etc… you get my drift.

To rename the subplan just double-click on the Subplan name.

Rename the Subplan and specify a description and simply click OK

Since I am going to use only one subplan for this post I am going to leave that name as Subplan_1.

Step 4: Drag the Back Up Database Task to the designer surface area

Now in the Toolbox pane to the left select and drag Back Up Database Task from within the Maintenance Plans Tasks to the designer surface area and release.

Step 5: Edit the task

Right click on the Back Up Database Task and select Edit…

Step 6: Perform a quick hat trick (hockey reference)

A) Click the Database(s) select list
B) Select System databases
C) Click OK

Step 7: Specify the backup path in the Folder: field and click OK

If the Folder: is already populated using a local file system path then you can leave it as is. It will work as is. I am using a network share just as an example to illustrate that you would normally want to backup to a network share which should be routinely backed up via an enterprise backup system.

Step 8: Drag the Maintenance Cleanup Task to the designer surface area and release. The Maintenance Cleanup Task will purge all files with a specific file extension using a given date specification.

Step 9: Set the workflow

A) Click the Back Up Database Task
B) Drag the Green Arrow to the Maintenance Cleanup Task and release

This means when the backup task completes successfully to proceed and execute the Maintenance Cleanup Task.

Step 10: Edit the Maintenance Cleanup Task

This is similar to Step 5 except you are right clicking on Maintenance Cleanup Task instead and selcting Edit…

Step 11: Four point play…

A) Specify the backup path in the Folder: field
B) Specify the extension bak in the File extention field
C) Specify a value unit of time in numbers
D) Specify a value unit of time for the time frame then click OK

Step 12: Scheduling the Maintenance Plan

Click the Calendar Icon just above the Maintenance Plan name

Step 13: Secondary hat trick…

A) I like to remove the .Subplan_1 from the Maintenance Plan name (optional)
B) Click the occurs: select list and choose Daily
C) Set the field occurs once at: to when you want this to kick off and click OK

Step 14: Close & save the Maintenance Plan

Click Yes to confirm


Done! Well at least with creating the Maint Plan. We just need to test it.

Step 15: Start the newly created SQL Job

Right click on Daily_System_Database_Full_Backup.Subplan_1 and select Start Job at Step…

If the process fails make sure your service account has Change permissions on the network share. If you are running the SQL Agent Service under the Network Service account then set the permissions as illustrated. This also applies to what ever account you are running the Agent Service under like a domain account and such.

Otherwise if everything is configured correctly you will see GREEN!

And the databases will have been backed up as such…

Amended 2011-05-10

You should read Brad McGehee’s eBook: Brad’s Sure Guide to SQL Server Maintenance Plans to get a better understanding of some of the gotchas you need to be aware about in regards to Maintenance Plans.