Red Gate forums: SQL Storage Compress 6

RE: Error trying to restore to compressed database

Lala55 — Wed, 22 May 2013 06:49:20 GMT

You can also manage the HyperBac Control Service directly from Windows (for example, in Windows XP, go to Control Panel > Administrative Tools > Services > HyperBac Control Service).

If you stop the HyperBac Control Service while it is processing backup data for a SQL Server operation, the SQL Server operation will fail.

RE: SQL Storage Compress has been retired

DanielleShriek — Mon, 13 May 2013 06:21:29 GMT

I have used SQL HyperBac and encountered an error called "The volume on device <backup_path> is empty" what does it mean? How can I resolve it?

Big Data Companies

RE: Query same as GUI - current size vs. compressed

epetro — Thu, 18 Apr 2013 19:25:17 GMT

I received notice from support that they use C# and TSQL to gather this data and, as a user, I will not have access to this information.

I wrote a script that would grab similar information and mark my compressed databases with a '1'. I then copied that to excel and filled in another column of %savings by hand.

Code:

use [Master]
SELECT [db]= db_name(sys.master_files.[database_id])
,CASE type_desc
WHEN 'ROWS' THEN 'Data'
WHEN 'LOG' THEN 'Log' END AS [File Type]
,sum( [size]*8.0/1024 ) AS [File Size_MB]
,sum( [size]*8.0/1024/1024 ) AS [File Size_GB]
,case when t1.database_id is NULL then 0 else 1 end [is compressed]
FROM sys.master_files
left join (select distinct [database_id] from sys.master_files where physical_name like '%x')t1 on sys.master_files.database_id=t1.database_id
group by type_desc,t1.[database_id],sys.master_files.database_id

Query same as GUI - current size vs. compressed

epetro — Wed, 17 Apr 2013 22:38:30 GMT

I have been asked to provide data for a server move which should include the size of each database both native and compressed. I would really like to match the data available in the GUI on the 'Database Sizes' tab.

If anyone knows how/where to pull that data, please post.

Thanks.

(If I get this info from support I will provide it in an update)

SQL Storage Compress has been retired

fionag — Tue, 05 Mar 2013 14:06:52 GMT

After a review of our database administration software, we've decided to focus development on our core database administration tools, and to retire the HyperBac powered products (SQL HyperBac, SQL Storage Compress, and SQL Virtual Restore).

If you already own one of these tools, you can continue to use our forums for help and support � just post your query here.

RE: Databases start up 'In Recovery' in V5.4.0.22 (and 5.4.1.5)

mglenn — Thu, 21 Feb 2013 18:18:04 GMT

skyline69 wrote:

This is still an on-going issue Chris!?

The fact that it's February 2013 and there's still no response to this question is not encouraging.

RE: Running ETL Process against Compressed Database

eddie davis — Fri, 23 Nov 2012 11:04:40 GMT

Hi, Thank you for your post into the forum and sorry that you have encountered a problem.

A support call has been created for you, the call reference is F0067031.

Can you please send an e-mail to support@red-gate.com with the above call reference number in the subject field? In your e-mail can you please confirm the following information and attach the requested HyperBac files?

Once we receive the requested information, we will be able to offer advice and hopefully identify a cause of the performance degradation.

Many Thanks
Eddie

Running ETL Process against Compressed Database

Kadams — Wed, 21 Nov 2012 22:03:55 GMT

Hi,

I have been testing our ETL process against the compressed database and the uncompressed database to verify performance and so far ETL against the compressed database is taking up to 4x longer to run. Is this to be expected?

I was under the impression that the compressed database would perform as well or better than the uncompressed database.

RE: Error trying to restore to compressed database

Playbill — Tue, 13 Nov 2012 13:19:11 GMT

I'm getting the same error in one of our development database servers. Tried changing the service account but still no luck. Any other way to solve this? It works well in my local workstation but I need to try it now to our actual databases. Please help. Thanks!

RE: Error trying to restore to compressed database

squillman — Tue, 09 Oct 2012 21:21:53 GMT

I got this to work. I had to change the HyperBac service to log in as a standard account with local administrator access instead of LOCAL SERVICE. Once I changed the log on account and restarted HyperBac it worked.

Error trying to restore to compressed database

squillman — Tue, 09 Oct 2012 19:53:38 GMT

I have just installed the SQL Storage Compress 6.1 trial and am trying to restore to a compressed database. Every time I try I get an error during the Configure HyperBac Control Service stage. The error message is "HyperBac Control Service did not update status.dat file".

I've tried 2 different databases, each of which was backed up (natively) from my local instance specifically to restore using Storage Compress. I've restarted the SQL server instance, HyperBac service, and even reinstalled HyperBac.

Environment:
- Win7 Pro x64
- SQL 2008 R2 Dev x64

Any suggestions what I can try next to get this working?

HyperBac Components Update (version 5.9.0)

fionag — Wed, 03 Oct 2012 10:37:58 GMT

Version 5.9 of the HyperBac components have been released (SQL Storage Compress is powered by HyperBac technology).

Build numbers:
Installer version: 5.9.0.2
Service version: 5.9.0.13
Driver version: 6.3.0.34
SQL Storage Compress: 6.1.0.157

New Features / Bugs Fixed

- Fixed bug that occasionally caused compressed databases to grow larger than their SQL Server size. (HBT-191)

SQL Storage Compress (v6.1) and HyperBac Components (v5.8.0)

fionag — Wed, 05 Sep 2012 09:40:45 GMT

SQL Storage Compress (v6.1) and HyperBac Components (v5.8.0) have been released.
(SQL Storage Compress is powered by HyperBac technology)

Build numbers:
Installer version: 5.8.0.3
Service version: 5.8.0.246
Driver version: 6.3.0.34
SQL Storage Compress: 6.1.0.157

New Features / Bugs Fixed

SQL Storage Compress
- SQL Storage Compress online help has been reviewed and updated.
- It is now possible to create a compressed database on a SQL Server 2012 instance via the SQL Storage Compress GUI. (HBO-178)
- SQL Storage Compress GUI will now correctly report the �Summary of savings�, for SQL Server 2012 instances with zero or one databases. (HBO-181)

HyperBac Engine / HyperBac Driver / Utilities
- HyperBacSupportInfo.zip: Output file is now called SupportLogsAndSystemData.zip.
- The HyperBac Driver should no longer cause a Blue Screen if an error occurs while the driver is being loaded into the Kernel. (HBD-11)

HyperBac Components Update (version 5.7.0)

fionag — Tue, 10 Jul 2012 08:48:36 GMT

Version 5.7 of the HyperBac components have been released (SQL Storage Compress is powered by HyperBac technology).

Build numbers:
Installer version: 5.7.0.4
Service version: 5.7.0.155
Driver version: 6.2.0.84

Since last August we have released 3 versions of the components as follows:

Version 5.7.0 (July 2012)

- A bug causing restores to SSC databases to fail on some hardware (HyperBac logs showed the error "Failed to probe user buffer") has been fixed. (HBD-27)
- Windows Explorer now displays .mdfe, .ndfe, and .ldfe files with the HyperBac icon. (HBT-197)

Version 5.6.x (May 2012)

- Index files that are no longer needed are now deleted automatically.
- Various bugs surrounding handling SQL Storage Compress (SSC) and SQL Virtual Restore (SVR) databases on a mounted virtual hard disk have been fixed. (HBT-183)
- Compressed database files and stub SVR files can now be copied and remounted safely. (HBT-149)
- HyperUtil now respects the -L option (which overrides the log file path). (HBT-212)

Version 5.5.x (November 2011 and February 2012)

- The service now reports its progress when rebuilding index files; this is written to the associated log file. (HBT-179)
- SSC and SVR databases can now be brought on-line instantly. This greatly reduces the time taken to initialise these databases on system start up.
- RESTORE WITH REPLACE to an SSC database now gives the expected compression even after repeated RESTORE operations. (HBT-107)
- A memory leak that could be seen as a small increase in memory used every few hours has been fixed.

RE: MODIFY FILE encountered operating system error 112

RajK — Tue, 03 Jul 2012 12:30:06 GMT

I am the support engineer that is investigating this issue since the date you have reported this issue. I was hoping to get some more information from you in regards to this error and this sytem.

Is it possible to send me the following information to get more clearer picture of what is happening on your system?

I was hoping to get the following:

- OS version
- Number of CPU's and Cores, and Memory on the machine
- SQL Server version
- Status.dat, openstatus.dat and hyperbac.conf from C:\Program Files (x86)\Red Gate\HyperBac\bin
- Service.log and any other logs in C:\Program Files (x86)\Red Gate\HyperBac\logs
- The format version of the Backup file that you are using in this test?
- Does the test succeed if you try the restore with a different drive?
- Are you able to send me the exact restore command when you try this via SQL Mgt studio?

Thanks for your patience and feedback in this matter.