Customer Reviews

Professional SQL Server 7.0 Development Using SQL-DMO, SQL-NS & DTS

5 star:		(1)
4 star:		(1)
3 star:		(1)
2 star:		(2)
1 star:		(1)

 

 

This is the first book to come out on DTS that I'm aware of. Unfortunatly, this book is heavily focused on the development of VB apps that work with SQL Server. There is a pretty good DTS object heirarchy in the appendix, but the 2 chapters on DTS cover only the basics.

I bought this book to assist me with a project that required moving and manipulating data between heterogeneous data sources. DTS seemed to be the right tool to do this and that proved to be true in the end.

However, this book was not a great assistance. The authors fill the book with various VB examples, which would be great, if I was augmenting my DTS packages with VB - but I wasn't. Rather, what would have been of great, are examples of raising errors, handling non-tabular input and output, and any nuances not revealed in Microsoft's help documents (which ended up being my main source of help).

In short, unless you are looking strictly for VB answers to DTS questions, I'd wait to see what other books come out. And they will, because DTS actually works great once its set up correctly.

This is an absolute rehash of the SQL Server Books Online, the samples are too. It is very light on DMO, SQL Namespace Objects and DTS. It is all very basic, does not explain the main concepts of SQL-DMO, does not explain the meta data cache for example. The biggest part of the book are the Appendix which are object models and rehashes of Microsoft matrials.

I found this book to be a big help in creating SQL DMO applications. I got some ideas for incorporating server and application roles via DMO, automating free log space counting and archiving via detach and attach, a way to limit extending the server's context for xp_cmdshell and ways to produce lists for users that are absent from EM (it may be simple, but there *is* no list of triggers for example, and the DMO EnumXXXX methods are a lot easier to deal with than ado's moreresults, when queries return more than one result set). I am a vfp programmer, but in manipulating an object model, the ideosynchrosies of the language aren't supposed to count for much, so I found it straightforward to translate the vb into vfp, and found my way.

I was discouraged from getting this book for a while because of the other reviews on this page, but when I really needed an additional reference for SQL-DMO, I went ahead for whatever I could get from the book. I have read through the portion of the book (The chapters, not the appendices - they are more for reference).
First, the book is not just a rehash of the SQL SBO, nor of the reference on MSDN. It was my frustration with searching through them, getting explanations that did not always offer enough of an example to really clear up the concept in my mind that led me to seek another book. The chapters in this book do lead the reader through examples, and do solidify the concepts I was looking to have solidified such as the practicalities of the object Heirarchy. Once you have this part firmly in mind, then MSDN, and SQL SBO's endless diagrams and cryptic descriptions begin to make more sense.

As for the examples being in VB, I program in C++ and Perl. I very, very seldom use VB or any of its variants, but it is so simple that there is no problem whatsoever in translating the examples from the VB in the book to the languages I use. The object model is the same regardless of the language, the languages just have a little different notation in accessing the properties and methods. For example:

VBS:

Private dSrv
Private dDb
Set dSrv = CreateObject("SQLDMO.SQLServer")
call AddSurvey("MyCompany", "MySurvey", "MyDbName")
Call dSrv.Connect("(local)", "sa", "changed")
Set dDb = CreateObject("SQLDMO.Database")
dDb.Name = "myDb"
dSrv.Databases.Add(dDb)

'set some db options:
private dbOption
set dbOption = dDb.DBOption
dbOption.SelectIntoBulkCopy = 0
dbOption.TruncateLogOnCheckpoint = 0
dbOption.AutoCreateStat = 0
dbOption.AutoShrink = 1
dbOption.AutoUpdateStat = 0

MsgBox dDb.Script

Is this in Perl:

use Win32;
use Win32::OLE;

my $srv = Win32::OLE->new('SQLDMO.SQLServer');

$srv->Connect('(local)', 'sa', 'changed');
my $db = Win32::OLE->new('SQLDMO.Database');
$db->{Name} = 'MyDb';
$srv->Databases->Add($db);
my $option = $db->DBOption();
$option->{SelectIntoBulkCopy} = 0;
$option->{TruncateLogOnCheckpoint} = 0;
$option->{AutoCreateStat} = 0;
$option->{AutoShrink} = 1;
$option->{AutoUpdateStat} = 0;

Win32::MsgBox($db->Script());

As anyone can see that takes even a few seconds to look at those two scripts for creating a database, the object model is exactly the same. The scripts are doing exactly the same thing. The only difference is in the language syntax, and there is such a direct correlation even there that it is very easy to translate from the examples in the book into the languages I prefer to use. For C++, chapter 12 is dedicated to setting up and creating projects in C++. From there, it is just using the C++ syntax to access the same object heirarchy.

In my opinion, the book does what it says it does, and was helpful, and clear in developing a better understanding within me of using SQL-DMO, SQL-NS, and DTS in my development.

Steve Howard

I had to write some programs for work that involved getting into the DMO objects of SQL Server, and this book was simply invaluable to me in understanding the objects better and helping me to produce a program that I am really proud of.

I have not checked out the other sections of this book, however the books from this lot (wrox) tend to be very good, with useful, real-life examples and detailed explanations. I also used a similar book from them to learn ASP.

I highly recommend this book.