Showing posts with label restores. Show all posts
Showing posts with label restores. Show all posts

Monday, March 12, 2012

OT: SQL Litespeed

Does anyone have any comments about SQL Litespeed re: backups and restores.
I would like to evaluate it but would like to hear some reviews.
Thanks,
EricGrab a demo copy off the website and check it out... Personally, I think
it's an excellent product.
I evaluated it at the request of my employer (before they would sign a
purchase order) and came up with the following:
I tested SQL Litespeed's backup and restore capabilities against that of the
native SQL Server BACKUP and RESTORE statements.
Two test databases were prepared. Both were 16gb.
The first database, 'BINARY', had a single table with a single BINARY(256)
column. I populated the column with random binary data produced by
generating and then concatenating 8 16-bit binary GUIDs per row. The goal
of this test was to see if speed increase would occur on data that
theoretically cannot be compressed.
The second database, 'TEXT', had a single table with a single TEXT column.
This column was populated with the full text of the Second Informal Review
Draft of the 1992 ANSI/ISO SQL Standard document (1.67 mb of raw text) per
row. The goal of this test was to see how much speed increase would occur
with highly compressible data.
A 'real' database will fall somewhere in-between these two examples,
probably closer to the text.
Results:
Backup Product Database Backup time
Backup size Restore Time
----
----
--
SQL Server BINARY 27:39
15.9 gb 32:08
SQL LiteSpeed BINARY 25:18
15.3 gb 24:34
SQL Server TEXT 19:13
16 gb 20:55
SQL LiteSpeed TEXT 11:32
4.6 gb 11:47
----
----
--
These tests seem to indicate that SQL LiteSpeed does live up to its claims
and performs better, delivering smaller backups and faster backups and
restores than the native BACKUP and RESTORE statements. I was very pleased
with its overall functionality and ease-of-use.
"Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> Does anyone have any comments about SQL Litespeed re: backups and
restores.
> I would like to evaluate it but would like to hear some reviews.
> Thanks,
> Eric
>|||I have been using it in production for a while now. It does what it says it
does. Backups are compressed and take less time and file space. Nothing
fancy or flashy, it just works.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> Does anyone have any comments about SQL Litespeed re: backups and
restores.
> I would like to evaluate it but would like to hear some reviews.
> Thanks,
> Eric
>|||Thanks Adam, great tests.
"Adam Machanic" <amachanic@.air-worldwide.nospamallowed.com> wrote in message
news:ef7PT2nPEHA.4064@.tk2msftngp13.phx.gbl...
> Grab a demo copy off the website and check it out... Personally, I think
> it's an excellent product.
> I evaluated it at the request of my employer (before they would sign a
> purchase order) and came up with the following:
> I tested SQL Litespeed's backup and restore capabilities against that of
the
> native SQL Server BACKUP and RESTORE statements.
> Two test databases were prepared. Both were 16gb.
> The first database, 'BINARY', had a single table with a single BINARY(256)
> column. I populated the column with random binary data produced by
> generating and then concatenating 8 16-bit binary GUIDs per row. The goal
> of this test was to see if speed increase would occur on data that
> theoretically cannot be compressed.
> The second database, 'TEXT', had a single table with a single TEXT column.
> This column was populated with the full text of the Second Informal Review
> Draft of the 1992 ANSI/ISO SQL Standard document (1.67 mb of raw text) per
> row. The goal of this test was to see how much speed increase would occur
> with highly compressible data.
> A 'real' database will fall somewhere in-between these two examples,
> probably closer to the text.
> Results:
> Backup Product Database Backup time
> Backup size Restore Time
> ----
--
> ----
--
> --
> SQL Server BINARY 27:39
> 15.9 gb 32:08
> SQL LiteSpeed BINARY 25:18
> 15.3 gb 24:34
> SQL Server TEXT 19:13
> 16 gb 20:55
> SQL LiteSpeed TEXT 11:32
> 4.6 gb 11:47
> ----
--
> ----
--
> --
> These tests seem to indicate that SQL LiteSpeed does live up to its claims
> and performs better, delivering smaller backups and faster backups and
> restores than the native BACKUP and RESTORE statements. I was very
pleased
> with its overall functionality and ease-of-use.
>
> "Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
> news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> > Does anyone have any comments about SQL Litespeed re: backups and
> restores.
> > I would like to evaluate it but would like to hear some reviews.
> >
> > Thanks,
> > Eric
> >
> >
>|||Thanks Geoff.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:Oqh7K$nPEHA.1036@.TK2MSFTNGP09.phx.gbl...
> I have been using it in production for a while now. It does what it says
it
> does. Backups are compressed and take less time and file space. Nothing
> fancy or flashy, it just works.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
> news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> > Does anyone have any comments about SQL Litespeed re: backups and
> restores.
> > I would like to evaluate it but would like to hear some reviews.
> >
> > Thanks,
> > Eric
> >
> >
>|||We use is too. We had one piece of hardware whose log backups would fail
intermittently but it was on its way out anyway. We haven't had any problems
since migrating those databases to new hardware. We run it on 15 different
servers. I think that the largest database is 20 GB or so.
It's a snap to implement b/c you can just replace the backup commands in
your procs with the litespeed commands. I think that it comes with a
maitenance plan tool, too but I haven't used that.
Michelle
"Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> Does anyone have any comments about SQL Litespeed re: backups and
restores.
> I would like to evaluate it but would like to hear some reviews.
> Thanks,
> Eric
>|||As a minor update, I've been pleased so far with SLS. I did learn that the
next version of the professional version will natively support object level
restorations which is pretty cool.
Eric
"Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
news:uNd58qnPEHA.620@.TK2MSFTNGP10.phx.gbl...
> Does anyone have any comments about SQL Litespeed re: backups and
restores.
> I would like to evaluate it but would like to hear some reviews.
> Thanks,
> Eric
>|||Anyone reading who can explain to me how this will work (from a lower-level
standpoint)? I was under the impression that the Virtual Device Interface
post-6.5 (was there even a VDI in 6.5?) only supports backup and restore at
the database level; how can restoration of only a single table be possible?
"Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
news:%23kv2fMyQEHA.3452@.TK2MSFTNGP10.phx.gbl...
> As a minor update, I've been pleased so far with SLS. I did learn that
the
> next version of the professional version will natively support object
level
> restorations which is pretty cool.|||Good point. Perhaps it's less glamorous than it sounds a la the way
enterprise manager "looks" like it's reordering columns for you by just
dragging a column to a new "location." It will be interesting to test it
(but I won't be getting the pro version) :-(
Eric
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:uAi8BcyQEHA.3348@.TK2MSFTNGP09.phx.gbl...
> Anyone reading who can explain to me how this will work (from a
lower-level
> standpoint)? I was under the impression that the Virtual Device Interface
> post-6.5 (was there even a VDI in 6.5?) only supports backup and restore
at
> the database level; how can restoration of only a single table be
possible?
> "Eric Sabine" <mopar41@.___ho_y_tmail.ScPoAmM> wrote in message
> news:%23kv2fMyQEHA.3452@.TK2MSFTNGP10.phx.gbl...
> > As a minor update, I've been pleased so far with SLS. I did learn that
> the
> > next version of the professional version will natively support object
> level
> > restorations which is pretty cool.
>

Saturday, February 25, 2012

osgl syntax problem

I have a script that runs fine in SQL Query Analyzer but has a syntax error
using osql. It restores several databases and log files. One of the database
s
has a space in the database name. Similar to RESTORE DATABASE "XXXX XXXX"
FROM DISK (BLAH). When run using osql all the databases restore correctly
except for the database with the space in the name. SQL Query Analyzer has n
o
problems with the statement. Is there any way to make this work or do I have
to rename the database with no spaces?
--
Mark Koenig
Tucson, AZIdeally, you should have no spaces in object names, or you get the problem
you encountered. Try:
SET QUOTED IDENTIFIER ON
GO
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada tom@.cips.ca
www.pinpub.com
"KMK" <kkoenig@.email(DOT)arizona(DOT)edu> wrote in message
news:BFFEDC2D-C3BE-4365-8369-F6F1C7D6D875@.microsoft.com...
>I have a script that runs fine in SQL Query Analyzer but has a syntax error
> using osql. It restores several databases and log files. One of the
> databases
> has a space in the database name. Similar to RESTORE DATABASE "XXXX XXXX"
> FROM DISK (BLAH). When run using osql all the databases restore correctly
> except for the database with the space in the name. SQL Query Analyzer has
> no
> problems with the statement. Is there any way to make this work or do I
> have
> to rename the database with no spaces?
> --
> Mark Koenig
> Tucson, AZ|||It's been awhile since I've used osql but with embedded spaces, you might
need to use brackets. i.e. [My Database] Perhaps, enclose in double quote
marks. Or, single and double quote marks.
If this was a stored procedure, a fully qualified name would be:
[My Server].[My Databse].[My Owner].[sp Select Data]
I did some batch osql about a year ago and I had to send filenames into SQL
Server to generate and execute some bulk insert statements.
In DOS, I passed the filename to a common script that called SQL Server. In
the calling script, I passed the filename as "'C:\Program Files...TXT'".
Note, the single quotes inside the double quotes. Then in the common script
that called SQL Server, I had the following line:
@.osql -E -S %SQLServerName% -d %Database% -Q "exec %1 %~2"
Note: Parameter %1 contained the name of the stored procedure to execute.
Parameter %~2 is the fully qualified name of the input file.
In the stored procedure, I received the filename as varchar(128). When I
concatenated it into the bulk insert statement, I had to enclose it in singl
e
quote marks in order to accomodate embedded spaces. For example, the
statement ended up as BULK INSERT...FROM 'C:\PROGRAM FILES...TXT'. To embed
single quote marks just repeat it. So it's EXEC ('bulk insert ' + @.TableNam
e
+ ' from ''' + @.DataFilename + ''' with (tablock, firstrow = ' +
@.StartRowNumber + ', formatfile = ''' + @.FormatFilename + ''', maxerrors = '
+ @.MaxNumberOfErrors + ')')
Bottom line, you need double quote marks to pass a filename with embedded
spaces from one DOS/batch command script to another. (I don't know if you'r
e
doing this part or not.) Then, it has to be enclosed in single quote marks
for the osql statement. (At least it did for me using the -Q (query)
parameter.) Then, if your concatenating it in a stored procedure, you need
to embed the incoming value in single quote marks.
Hope that helps,
Joe
"KMK" wrote:

> I have a script that runs fine in SQL Query Analyzer but has a syntax erro
r
> using osql. It restores several databases and log files. One of the databa
ses
> has a space in the database name. Similar to RESTORE DATABASE "XXXX XXXX"
> FROM DISK (BLAH). When run using osql all the databases restore correctly
> except for the database with the space in the name. SQL Query Analyzer has
no
> problems with the statement. Is there any way to make this work or do I ha
ve
> to rename the database with no spaces?
> --
> Mark Koenig
> Tucson, AZ|||This did work after using SET QUOTED_IDENTIFIER ON. Your response left out
the underline. Thanks for the info!
--
Mark Koenig
Tucson, AZ
"Tom Moreau" wrote:

> Ideally, you should have no spaces in object names, or you get the problem
> you encountered. Try:
> SET QUOTED IDENTIFIER ON
> GO
>
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada tom@.cips.ca
> www.pinpub.com
> "KMK" <kkoenig@.email(DOT)arizona(DOT)edu> wrote in message
> news:BFFEDC2D-C3BE-4365-8369-F6F1C7D6D875@.microsoft.com...
>
>