Re: How do I import/export databases in MSDE?

From: Richard Fagen (no_spam_at_my_isp.com)
Date: 03/25/04 

Date: Thu, 25 Mar 2004 08:55:43 -0500

Hi Andrea,

Thanks for that great explanation. When you mention T-SQL statements
and series of statement and DML (I come from an xBase - FoxPro, dBase,
Clipper world) it all started to make sense.

Scripts are like the old PRGs (files with FoxPro statement or DML) ...
now I get it! :)

Thanks for the likes to the sample Pubs and Northwind. This will help
with my learning as I intend to use those files extensively.

Richard

Andrea Montanari wrote:
> hi Richard,
> "Richard Fagen" <no_spam@my_isp.com> ha scritto nel messaggio
> news:uCyr0ibEEHA.3788@TK2MSFTNGP10.phx.gbl...
>
>>Hi,
>>
>>I didn't find backing up and restoring that complicated. Besides, those
>>are tasks I had to learn anyway :)
>>
>>Besides, I don't know anything about SQL scripts ... yet.
>>By scripts, do you mean those OSQL statement that can be put in a
>>'batch' file and run as a series of commands?
>>
>>How does one 'get' those scripts in the first place?
>
>
> Pubs and Northwind database samples are not present in MSDE distributions in
> order to limit deployment size, cut you can find an installer for them at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample/html/vcsamsampledatabaseinstallationutility.asp
>
> scripts are usually understood (in SQL Server world) as T-SQL statement or
> series of statements that perform some kind of database activities, like DDL
> (data definition language) operations, DML (data manipulation language), and
> so on...
> OSQL is only a client tool able to communicate with SQL Server via ODBC API,
> while iSQL uses DB-Library, another set of API to communicate with...
> T-SQL statements are sent to the server via the network protocols via the
> client side net-libs and the server, via another set of server side APIs
> present in the ODS (open data services) interface to commute the
> comunication into the private protocol used by SQL Server, known as TDS
> (tabular data stream), which is a self describind data stream composed by
> tokens describing the data transferred, such as column names, data types,
> events and status...
> so all statements and results are "encoded" both client side (ODBC. OLE-DB,
> DB-Lib) and server side (ODS) into the native communication TDS protocol...

Quantcast