I'm looking at copying a whole lot of data from our 3.2.1 ARSystem (Solaris/Sybase) to an separate SQLServer database on NT (no ARSystem on this system). This way we can manage access to historic information as a separate issue to our production system.

The method I'm considering is using some mechanism to get the data that I wish to archive into a separate schema (currently we use SQL Stored Procedures to do a similar job and will probably reuse this solution). Then use bcp to dump that table into a system file, copy that across to the NT server via ftp and then use SQLServer bcp to load the information into an identically defined table on that side.

The main questions I have relate to the compatibility of the two bcp utilities, any gotchas I need to watch for in the parameters I use when running bcp (e.g. -n -c or -f, etc). And are there any issues relating to diary fields. (I assume I won't be able to determine a termination character and so will have to use the -f option and specify the datatype and length of all columns :-()

Any comments would be appreciated. I realise this is more a db question than a Remedy one, but it is Remedy related as that is the source of the data.


regards, Barry

EOM

NOTICE - This message contains information intended only for the use of the addressee named above. It may also be confidential and/or privileged. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify The Broken Hill Proprietary Company Limited immediately via mailto:postmaster@bhp.com.au.

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

There are a couple of things that I can give you on this. The first is to be
aware of columns in your database which may contain records in which the
precision extends beyond two positions (such as rate information, ect.). The
reason is that bcp will truncate additional precision and not tell you.

About the delimiters... Bcp provides a couple of command line switches which
might help you out. They allow you to specify what you would like to have
for a delimiter, so that any custom app that you might write can EASILY read
the data file. The defaults for bcp-output data are a tab for columns and a
newline for the row.

To specify a custom delimiter for a column use the -t option, followed by a
quote, your delimiter and then another quote. For example, -t "xyz" would
delimit each of the columns with the string xyz.

To delimit a row with a custom delimiter, use the -r option and the same
format.


Will


-----Original Message-----
From: Cox, Barry BJ [mailto:Cox.Barry.BJ@BHP.COM.AU]
Sent: Wednesday, November 03, 1999 7:42 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Offline archiving


Listers,


I'm looking at copying a whole lot of data from our 3.2.1 ARSystem
(Solaris/Sybase) to an separate SQLServer database on NT (no ARSystem on
this system). This way we can manage access to historic information as a
separate issue to our production system.

The method I'm considering is using some mechanism to get the data that I
wish to archive into a separate schema (currently we use SQL Stored
Procedures to do a similar job and will probably reuse this solution). Then
use bcp to dump that table into a system file, copy that across to the NT
server via ftp and then use SQLServer bcp to load the information into an
identically defined table on that side.

The main questions I have relate to the compatibility of the two bcp
utilities, any gotchas I need to watch for in the parameters I use when
running bcp (e.g. -n -c or -f, etc). And are there any issues relating to
diary fields. (I assume I won't be able to determine a termination
character and so will have to use the -f option and specify the datatype and
length of all columns :-()

Any comments would be appreciated. I realise this is more a db question
than a Remedy one, but it is Remedy related as that is the source of the
data.


regards, Barry

EOM

NOTICE - This message contains information intended only for the use of the
addressee named above. It may also be confidential and/or privileged. If
you are not the intended recipient of this message you are hereby notified
that you must not disseminate, copy or take any action in reliance on it.
If you have received this message in error please notify The Broken Hill
Proprietary Company Limited immediately via mailto:postmaster@bhp.com.au.

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist