what does provigil show up as on a drug test use of phenergan and zofran together how long until unisom works does sominex improve sleep quality unisom and marijuana


SQL Server Database Error: 661

One of my customers had an issue where they failed to open a connection to a particular database they had been testing. The error read: ‘the database e:somepathsomefolderjermsmit.mdf’ cannot be opened because it is version 611. The server supports version 655 and earlier. A downgrade path is not supported.

This issue is caused because you are not permitted to use a database from a later release on an earlier system. i.e they are not backwards compatible

Problem: Databases created under a newer version of SQL Server are not compatible with previous versions of SQL Server

Solution(s) that I am aware of in this case:

  • You need to either upgrade your SQL Server instance to the same version as the database or one newer
  • Or copy out the data in that database into an earlier version (using the data migration wizard perhaps)

If you need to know the version of your source and destination databases use the following query:


The destination should be the same level or greater in in version.

Best of luck to ya

Exchange 2007 – Determine Whitespace

Today, I was ‘pinged’ with a question regarding a post I made some time ago regarding white space in Exchange databases. This post was referring to Exchange 2010. This has prompted me to do a quick update on finding out this info in Exchange 2007.

Here are my methods to gather this info:

  • Log into the Exchange 2007 Server
  • In the Exchange MMC Locate the Server and Mailbox Store of your choosing and dismount it (not necessary)
  • Then in the command prompt ran the following:  eseutil /ms databasename.edb (you may need to specify the full paths to the database file. Depending on the size of your database this may take some time.

Another way –

  • Open up your Exchange 2007 server’s even log viewer and look under Applications,
  • then filter for the even 1211 and sort by data/time and you should see the sour database name and in the event message you will notice something such as:  The database “Storage GroupDatabase” has 3 megabytes of free space after online defragmentation has terminated.

I hope this helps

Simple Exchange 2010 Database White Space Report

I was looking at some of my database on Exchange that seemed to be very large in size so first thought was that an offline defrag may be needed, but before I reach that point I wanted to know how much ‘slack’ or white space existed in each of my Exchange databases.

This was done by using the following command syntax in the Exchange Management Shell:

Get-MailboxDatabase -Status | Select-Object Server,Name,AvailableNewMailboxSpace

To export this into a CSV format the following can also be done, so that you can give to any management members for review of your findings:

Get-MailboxDatabase -Status | Select-Object Server,Name,AvailableNewMailboxSpace | Export-Csv C:workwhite_space_report.csv -Force -NoType

Next, I may find a way to setup this to email a weekly report…

SQL Server backup in multiple parts

“It’s so logical and so simple. Fat is the backup fuel system. The role it plays in the body is that when there’s no carbohydrate around, fat will become the primary energy fuel. That’s pretty well known.” – Robert Atkins

Recently I have been working with my dB Administrator to get some DR backups to our offsite location. Simple task made difficult with a few challenges: Size of the database, Bandwidth to transfer to remote site, and method of transfer. We got past part of the size issues by compressing the SQL database backups, but we still had issues getting the files to the remote site in time. So we switched from using Microsoft DFSR to using cygwin and Rsync. However there was another issue at play; We could never seem to get the full backup there in time.

Out bottle neck at this point was the available bandwidth needed to transfer and the files. The transfer would break and well it needed to do a checksum on the file to resume. At 200GB into it all this process to a considerable amount of time to only again fail.

That is when I got creative and suggested to use SQL to span/split the backup into multiple parts so that in the event the transfer would break and resume it only had to do some from just a single part of the total sum of data. You know what?  It works. It’s been 2 weeks now and our backups reach the remote site.

And here is what you can do the split up your backups:

DISK = 'D:BackupsNightlyCopyLARGEDB _01.bak'
,DISK = 'D:BackupsNightlyCopyLARGEDB _02.bak'
,DISK = 'D:BackupsNightlyCopyLARGEDB _03.bak'

And now the backup is split into equal parts of the original backup file size. In my production environment we split our compressed database into 64 parts giving us about 4GB per file.

I hope this helps you,

– Jermal

ESEUtil to Defrag an Exchange 2010 Mailbox Database

A garden is a complex of aesthetic and plastic intentions; and the plant is, to a landscape artist, not only a plant – rare, unusual, ordinary or doomed to disappearance – but it is also a color, a shape, a volume or an arabesque in itself. – Roberto Burle Marx



How To use ESEUtil to Defrag an Exchange 2010 Mailbox Database

We start this process by first opening the Exchange Management Shell and navigate to the folder containing the database file.

We then dismount the database

[PS] E:MailboxAB>Dismount-Database <name of database>

We now run ESEUtil to defrag the file using the /d switch to defrag

[PS] E:MailboxAB>eseutil.exe /d .<database name>

When completed we mount the database again.

[PS] E:MailboxAB>Mount-Database <database name>

Please see the following screen cap for refrence

And as always be sure that you have a backup that you can use for recovery if something goes wrong during the defrag.