InterBase's FOR SELECT..SUSPEND equivalent in MS SQL Server 2005

Hello everyone. I've been wrestling with this one for a while now
and am hoping you can help.
My company is moving from InterBase to MS SQL Server 2005 in the very
near future and all has gone well so far, but there is a stored
procedure on the InterBase database that I have had trouble finding an
equivalent method for on SQL Server.
I hope some of you are familiar with Interbase's FOR SELECT...
SUSPEND method used in sored procedures, but I will try to explain it
anyways. The stored procedure I'm working does something like the
following.
BEGIN
FOR
SELECT DISTINCT PERSONID,
FROM TRANSACTION
WHERE GENERALLEDGERCODE = :IN_GLCODE
INTO :V_PERSONID
DO
BEGIN
SELECT CLOSEDTRANSACTIONBALANCE
FROM SP_CLOSEDTRANSACTIONBALANCE(:V_PERSONID,
:IN_FIRSTDATE)
INTO :BALANCE1;
SELECT CLOSEDTRANSACTIONBALANCE
FROM SP_CLOSEDTRANSACTIONBALANCE( :V_PERSONID, :IN_ENDDATE)
INTO :BALANCE2;
IF( :BALANCE1 <> 0 OR :BALANCE2 <> 0 ) THEN
BEGIN
SUSPEND;
END
END
END
When and if SUSPEND is reached a row is returned from the stored
procedure of your declared return variables. Which in this case would
be PERSONID, BALANCE1, and BALANCE2.
When first attempting this, I just broke the procedure into a couple
different queries on the client side, but that caused something that
took 15 minutes to run on InterBase to take 10+ hours to run.
All of the examples of T-SQL and CLR stored procedures I have looked at
don't do anything quite like this.
Any advice you might have would be appreciated.> Hello everyone. I've been wrestling with this one for a while now
> and am hoping you can help.
> My company is moving from InterBase to MS SQL Server 2005 in the very
> near future and all has gone well so far, but there is a stored
> procedure on the InterBase database that I have had trouble finding an
> equivalent method for on SQL Server.
> I hope some of you are familiar with Interbase's FOR SELECT...
> SUSPEND method used in sored procedures, but I will try to explain it
> anyways. The stored procedure I'm working does something like the
> following.
>
> BEGIN
> FOR
> SELECT DISTINCT PERSONID,
> FROM TRANSACTION
> WHERE GENERALLEDGERCODE = :IN_GLCODE
> INTO :V_PERSONID
> DO
> BEGIN
> SELECT CLOSEDTRANSACTIONBALANCE
> FROM SP_CLOSEDTRANSACTIONBALANCE(:V_PERSONID,
:IN_FIRSTDATE)
> INTO :BALANCE1;
> SELECT CLOSEDTRANSACTIONBALANCE
> FROM SP_CLOSEDTRANSACTIONBALANCE( :V_PERSONID, :IN_ENDDATE)
> INTO :BALANCE2;
> IF( :BALANCE1 <> 0 OR :BALANCE2 <> 0 ) THEN
> BEGIN
> SUSPEND;
> END
> END
> END
> When and if SUSPEND is reached a row is returned from the stored
> procedure of your declared return variables. Which in this case would
> be PERSONID, BALANCE1, and BALANCE2.
> When first attempting this, I just broke the procedure into a couple
> different queries on the client side, but that caused something that
> took 15 minutes to run on InterBase to take 10+ hours to run.
> All of the examples of T-SQL and CLR stored procedures I have looked at
> don't do anything quite like this.
> Any advice you might have would be appreciated.
You might want to take a look at Table Functions in the BOL.
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com|||The closest you'll get to the FOR SELECT.. SUSPEND in SQL Server is using
Cursors.
Something else to be cautious of is the lack of Row-Level triggers in SQL
Server, so you'll need to consider that if you have any logic in Triggers.
And no Generators either, you'll need to use the Identity property on your
tables if you're using Trigger & Generators for primary keys.
There was a page on www.ibphoenix.com that did a pretty decent job of
comparing functionality, but I'm at a loss to find it..
<Contraptor@.gmail.com> wrote in message
news:1132327819.104004.209220@.g47g2000cwa.googlegroups.com...
> Hello everyone. I've been wrestling with this one for a while now
> and am hoping you can help.
> My company is moving from InterBase to MS SQL Server 2005 in the very
> near future and all has gone well so far, but there is a stored
> procedure on the InterBase database that I have had trouble finding an
> equivalent method for on SQL Server.
> I hope some of you are familiar with Interbase's FOR SELECT...
> SUSPEND method used in sored procedures, but I will try to explain it
> anyways. The stored procedure I'm working does something like the
> following.
>
> BEGIN
> FOR
> SELECT DISTINCT PERSONID,
> FROM TRANSACTION
> WHERE GENERALLEDGERCODE = :IN_GLCODE
> INTO :V_PERSONID
> DO
> BEGIN
> SELECT CLOSEDTRANSACTIONBALANCE
> FROM SP_CLOSEDTRANSACTIONBALANCE(:V_PERSONID,
:IN_FIRSTDATE)
> INTO :BALANCE1;
> SELECT CLOSEDTRANSACTIONBALANCE
> FROM SP_CLOSEDTRANSACTIONBALANCE( :V_PERSONID, :IN_ENDDATE)
> INTO :BALANCE2;
> IF( :BALANCE1 <> 0 OR :BALANCE2 <> 0 ) THEN
> BEGIN
> SUSPEND;
> END
> END
> END
> When and if SUSPEND is reached a row is returned from the stored
> procedure of your declared return variables. Which in this case would
> be PERSONID, BALANCE1, and BALANCE2.
> When first attempting this, I just broke the procedure into a couple
> different queries on the client side, but that caused something that
> took 15 minutes to run on InterBase to take 10+ hours to run.
> All of the examples of T-SQL and CLR stored procedures I have looked at
> don't do anything quite like this.
> Any advice you might have would be appreciated.
>|||Ok, I think I have a workable solution. I've created a UDF that
cursors through the initial query inserting rows into a table variable
if the right conditions are met. I have a couple questions though as I
have been unable to test it.
1. When trying to execute the function within the IDE it times out
after about a minute, when I know for a fact that it will take longer
than a minute to run. Finding a CommandTimeOut setting to change from
say 1 minute to 5 minutes has so far been elusive.
2. Since I was unable to test in Studio 2005, I went back to my main
work environment (Borland C++ Builder 6 (don't laugh) ) where this UDF
is ultimately to be used, I dropped a TADOStoredProc, setup my
parameters, set the CommandTimeOut to 15000 seconds instead of 30,
setup a couple other necessary things and when I run it I got a
""TRXACCOUNTLIST" Failed because "TRXACCOUNTLIST" is a table valued
function object" error. This wasn't totaly surprising to me, so I
wrapped the UDF in a stored procedure, but when I run that stored proc
from within Studio 2005 I receive an error saying "The request for
procedure 'TRXACCOUNTLIST' failed because 'TRXACCOUNTLIST' is a table
valued function object.".
Any Suggestions? I can provide code, but I wasn't sure if that would
be helpful here as I may be trying to do something fundamentally wrong.
I'm running Studio 2005 against SQL Server 2005, latest releases.|||1. There is a CommandTimeOut property on the SQLCommand object, you might
want to toggle that.
2. Do you have the latest service packs for BCB? That last Borland
environment I used was D6 and it had issues with ADO & SQL Server 2000
objects. There was an ADOExpress(is that the name?) update that corrected
some issues with SQL Server 2000, if I remember correctly. Can you run the
UDF in query analyzer or SQL Server Management studio without error? If not,
post your code and we'll take a look at it. If the query runs, you might
want to check out the borland newsgroups.
<Contraptor@.gmail.com> wrote in message
news:1132610782.388887.231870@.z14g2000cwz.googlegroups.com...
> Ok, I think I have a workable solution. I've created a UDF that
> cursors through the initial query inserting rows into a table variable
> if the right conditions are met. I have a couple questions though as I
> have been unable to test it.
> 1. When trying to execute the function within the IDE it times out
> after about a minute, when I know for a fact that it will take longer
> than a minute to run. Finding a CommandTimeOut setting to change from
> say 1 minute to 5 minutes has so far been elusive.
> 2. Since I was unable to test in Studio 2005, I went back to my main
> work environment (Borland C++ Builder 6 (don't laugh) ) where this UDF
> is ultimately to be used, I dropped a TADOStoredProc, setup my
> parameters, set the CommandTimeOut to 15000 seconds instead of 30,
> setup a couple other necessary things and when I run it I got a
> ""TRXACCOUNTLIST" Failed because "TRXACCOUNTLIST" is a table valued
> function object" error. This wasn't totaly surprising to me, so I
> wrapped the UDF in a stored procedure, but when I run that stored proc
> from within Studio 2005 I receive an error saying "The request for
> procedure 'TRXACCOUNTLIST' failed because 'TRXACCOUNTLIST' is a table
> valued function object.".
> Any Suggestions? I can provide code, but I wasn't sure if that would
> be helpful here as I may be trying to do something fundamentally wrong.
>
> I'm running Studio 2005 against SQL Server 2005, latest releases.
>|||The query runs alright. Last night it pegged our test box at 100% cpu
utilization for several hours before I came in a closed things down.
I forgot that a feature of Table-Value UDFunctions is that I could just
run a select from it and didn't need to wrap it in a stored procedure
at all.
Now I just need to figure out why something that takes 10-15 minutes to
run in InterBase takes hours within a more powerful SQL Server 2005
box. Hopfully it's just a matter of setting up some indexes.|||Inserting the indexes did the trick, now the whole process runs in
under 5 minutes in MS SQL Server.

Interbase to SQL Server 2000 Question

I've posted this question on a few InterBase/Firebird newsgroups but with no
response.
About 7 years ago, I created an InterBase application for a client using
InterBase 4.x. I haven't worked with InterBase since. They now want to
convert this to SQL Server. Actually, all we want to do is to convert the
tables and the data in the tables to SQL Server 2000. The other schema
objects won't get converted. I downloaded the latest version of InterBase
from Borland (V6.x or V7.0, don't recall which). When I attempted to open
the InterBase database, I get an error saying the on-disk structure is
unsupported. Could anyone offer a suggestion on what I can do?
Thanks very much.
Hi
Looks like they changed the format between these versions! If you don't have
a working system, then I guess that you may have to resort to somewhere like
ebay to get one! If you do have a working system, then you might be able to
connect from SQL Server via ODBC and use DTS to get the tables/data.
John
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>
|||Amos,
I have had to do exactly this for a client. It's not too hard, but it is a
bit fiddly.
The on-disk formats are different, for 4.x and 7.x, so you can't just open
the files. What you have to do is to backup the Interbase 4.x database using
the utility in the 4.x installation, then restore it using the same utility
in the 7.x installation. The backed up file contains all the metadata so 7.x
can re-create it. The utility is called something like gbak, and all the
details are in the Interbase documentation.
Once you've got the data into Interbase you need a 3rd party ODBC driver to
get the data out. I used one of the free ones, forget which. I had to
REMOVE all the triggers from the tables before I could connect with the ODBC
driver though, whch was a pain as there were a lot of them. I eventually
figured out how to automate it, but it is OK to do manually.
If you want to contact me directly take the 'nospam' out of my e-mail
address.
Regards,
Richard
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>

Interbase to SQL Server 2000 Question

I've posted this question on a few InterBase/Firebird newsgroups but with no
response.
About 7 years ago, I created an InterBase application for a client using
InterBase 4.x. I haven't worked with InterBase since. They now want to
convert this to SQL Server. Actually, all we want to do is to convert the
tables and the data in the tables to SQL Server 2000. The other schema
objects won't get converted. I downloaded the latest version of InterBase
from Borland (V6.x or V7.0, don't recall which). When I attempted to open
the InterBase database, I get an error saying the on-disk structure is
unsupported. Could anyone offer a suggestion on what I can do?
Thanks very much.Hi
Looks like they changed the format between these versions! If you don't have
a working system, then I guess that you may have to resort to somewhere like
ebay to get one! If you do have a working system, then you might be able to
connect from SQL Server via ODBC and use DTS to get the tables/data.
John
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>|||Amos,
I have had to do exactly this for a client. It's not too hard, but it is a
bit fiddly.
The on-disk formats are different, for 4.x and 7.x, so you can't just open
the files. What you have to do is to backup the Interbase 4.x database using
the utility in the 4.x installation, then restore it using the same utility
in the 7.x installation. The backed up file contains all the metadata so 7.x
can re-create it. The utility is called something like gbak, and all the
details are in the Interbase documentation.
Once you've got the data into Interbase you need a 3rd party ODBC driver to
get the data out. I used one of the free ones, forget which. I had to
REMOVE all the triggers from the tables before I could connect with the ODBC
driver though, whch was a pain as there were a lot of them. I eventually
figured out how to automate it, but it is OK to do manually.
If you want to contact me directly take the 'nospam' out of my e-mail
address.
Regards,
Richard
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>

Interbase to SQL Server 2000 Question

I've posted this question on a few InterBase/Firebird newsgroups but with no
response.
About 7 years ago, I created an InterBase application for a client using
InterBase 4.x. I haven't worked with InterBase since. They now want to
convert this to SQL Server. Actually, all we want to do is to convert the
tables and the data in the tables to SQL Server 2000. The other schema
objects won't get converted. I downloaded the latest version of InterBase
from Borland (V6.x or V7.0, don't recall which). When I attempted to open
the InterBase database, I get an error saying the on-disk structure is
unsupported. Could anyone offer a suggestion on what I can do?
Thanks very much.Hi
Looks like they changed the format between these versions! If you don't have
a working system, then I guess that you may have to resort to somewhere like
ebay to get one! If you do have a working system, then you might be able to
connect from SQL Server via ODBC and use DTS to get the tables/data.
John
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>|||Amos,
I have had to do exactly this for a client. It's not too hard, but it is a
bit fiddly.
The on-disk formats are different, for 4.x and 7.x, so you can't just open
the files. What you have to do is to backup the Interbase 4.x database using
the utility in the 4.x installation, then restore it using the same utility
in the 7.x installation. The backed up file contains all the metadata so 7.x
can re-create it. The utility is called something like gbak, and all the
details are in the Interbase documentation.
Once you've got the data into Interbase you need a 3rd party ODBC driver to
get the data out. I used one of the free ones, forget which. I had to
REMOVE all the triggers from the tables before I could connect with the ODBC
driver though, whch was a pain as there were a lot of them. I eventually
figured out how to automate it, but it is OK to do manually.
If you want to contact me directly take the 'nospam' out of my e-mail
address.
Regards,
Richard
"Amos Soma" <amos_j_soma@.y_a_hoo.com> wrote in message
news:HYudnYvUxYfBgUXd4p2dnA@.buckeye-express.com...
> I've posted this question on a few InterBase/Firebird newsgroups but with
no
> response.
> About 7 years ago, I created an InterBase application for a client using
> InterBase 4.x. I haven't worked with InterBase since. They now want to
> convert this to SQL Server. Actually, all we want to do is to convert the
> tables and the data in the tables to SQL Server 2000. The other schema
> objects won't get converted. I downloaded the latest version of InterBase
> from Borland (V6.x or V7.0, don't recall which). When I attempted to open
> the InterBase database, I get an error saying the on-disk structure is
> unsupported. Could anyone offer a suggestion on what I can do?
> Thanks very much.
>

Interbase

Greetings all,
I would like help with how to do a one time import of data from
Interbase to MsSQL.
kindness
Abby
Hi
Look at SQL Server 2000's DTS ("Import and Export Data" in the SQL Server
Windows Menu)
With a Interbase driven installed on a machine, you can have DTs move the
data for you.
Books Online has a lot of information in DTS.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"abby" <abby@.trolling.org> wrote in message
news:cv5fc1$85n$1@.ctb-nnrp2.saix.net...
> Greetings all,
> I would like help with how to do a one time import of data from
> Interbase to MsSQL.
> kindness
> Abby
|||Mike Epprecht (SQL MVP) wrote:

> Hi
> Look at SQL Server 2000's DTS ("Import and Export Data" in the SQL Server
> Windows Menu)
> With a Interbase driven installed on a machine, you can have DTs move the
> data for you.
> Books Online has a lot of information in DTS.
I assume you meant an Interbase ODBC driver installed on the machine?
As this will be a onetime transfer I am trying to avoid having to
purchase such a driver for one time use.
Thanks

> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "abby" <abby@.trolling.org> wrote in message
> news:cv5fc1$85n$1@.ctb-nnrp2.saix.net...
>
>
|||Hi
All the tools the MS supply rely on a ODBC driver for the source DB. The
ODBC driver understands the source, and the tools then just have to do the
manipulation.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"abby" <abby@.trolling.org> wrote in message
news:cv6e7k$dql$1@.ctb-nnrp2.saix.net...[vbcol=seagreen]
> Mike Epprecht (SQL MVP) wrote:
Server[vbcol=seagreen]
the[vbcol=seagreen]
>
> I assume you meant an Interbase ODBC driver installed on the machine?
> As this will be a onetime transfer I am trying to avoid having to
> purchase such a driver for one time use.
> Thanks
>
|||Mike Epprecht (SQL MVP) wrote:

> Hi
> All the tools the MS supply rely on a ODBC driver for the source DB. The
> ODBC driver understands the source, and the tools then just have to do the
> manipulation.
Thanks

> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "abby" <abby@.trolling.org> wrote in message
> news:cv6e7k$dql$1@.ctb-nnrp2.saix.net...
>
> Server
>
> the
>
>

Interbase

Greetings all,
I would like help with how to do a one time import of data from
Interbase to MsSQL.
kindness
AbbyHi
Look at SQL Server 2000's DTS ("Import and Export Data" in the SQL Server
Windows Menu)
With a Interbase driven installed on a machine, you can have DTs move the
data for you.
Books Online has a lot of information in DTS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"abby" <abby@.trolling.org> wrote in message
news:cv5fc1$85n$1@.ctb-nnrp2.saix.net...
> Greetings all,
> I would like help with how to do a one time import of data from
> Interbase to MsSQL.
> kindness
> Abby|||Mike Epprecht (SQL MVP) wrote:

> Hi
> Look at SQL Server 2000's DTS ("Import and Export Data" in the SQL Server
> Windows Menu)
> With a Interbase driven installed on a machine, you can have DTs move the
> data for you.
> Books Online has a lot of information in DTS.
I assume you meant an Interbase ODBC driver installed on the machine?
As this will be a onetime transfer I am trying to avoid having to
purchase such a driver for one time use.
Thanks

> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "abby" <abby@.trolling.org> wrote in message
> news:cv5fc1$85n$1@.ctb-nnrp2.saix.net...
>
>
>|||Hi
All the tools the MS supply rely on a ODBC driver for the source DB. The
ODBC driver understands the source, and the tools then just have to do the
manipulation.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"abby" <abby@.trolling.org> wrote in message
news:cv6e7k$dql$1@.ctb-nnrp2.saix.net...[vbcol=seagreen]
> Mike Epprecht (SQL MVP) wrote:
>
Server[vbcol=seagreen]
the[vbcol=seagreen]
>
> I assume you meant an Interbase ODBC driver installed on the machine?
> As this will be a onetime transfer I am trying to avoid having to
> purchase such a driver for one time use.
> Thanks
>|||Mike Epprecht (SQL MVP) wrote:

> Hi
> All the tools the MS supply rely on a ODBC driver for the source DB. The
> ODBC driver understands the source, and the tools then just have to do the
> manipulation.
Thanks

> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "abby" <abby@.trolling.org> wrote in message
> news:cv6e7k$dql$1@.ctb-nnrp2.saix.net...
>
> Server
>
> the
>
>