Support
Q. Which versions of SQL Server are supported?
A. SQLMetaTool supports all editions of SQL Sever 2000, SQL Sever 2005 and SQL Sever 2008.
Both 32 and 64 bit versions are supported.
Q. Which Operating Systems are supported?
A. Desktop: Windows XP, Windows Vista, Windows 7.
Server:
Windows Server 2003, Windows Server 2008.
Windows 2000 is not supported but 'should' work although
you need to be on Service Pack 3 or later and have installed Windows Installer 3.0 or
later, .NET Frameworks 2.0 and security update KB835732.
Q. When I try to install SQLMetaTool under Windows 2000 I get an error message that
says 'The procedure entry point HeapSetInformation could not be found'.
A. SQLMetaTool is not officially supported under Windows 2000 but see previous
question.
The lack of KB835732 is the usual reason for this message.
Q. I have scanned several databases successfully but the system won't
let me scan any more.
A. Are you still in Evaluation Mode? You can only scan 6 databases in Evaluation Mode;
after this you need to purchase an Activation Code and then apply the Activation Code to
SQLMetaTool to change it to the Licensed Mode.
Q. I have a licensed copy of SQLMetaTool and have scanned lots of databases but it
won't let me scan a new server.
A. You purchased an Activation Code for a defined number of servers.
One option is to delete one of the existing servers (and associated databases) in the Configuration page.
This will then allow you to scan another new server.
AAlternatively you can purchase additional server licenses; the cost is normally just the difference between
what you paid and the current price - please contact us with your existing details and we'll sort it out.
Q. I have a single server license for SQLMetaTool and have moved all of my databases over to a new server.
I can't add the new server to SQLMetaTool without deleting all of my existing scans and the old server name.
A.
There is no built-in mechanism to migrate to a new server but if you open up the table tblServers in the
SQLMetaTool database and change the ServerName value from the old to the new server's name (including the
instance name if it's not the default instance) then this should allow you to scan the new server and
will retain all of the old data (don't just add a new row - the licensing will object
to that). Don't forget to back up the database first!