| Date: | Fri, 4 Nov 2011 14:48:33 -0500 |
| Reply-To: | AnnHett <annhett@GMAIL.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | AnnHett <annhett@GMAIL.COM> |
| Subject: | Re: most efficient way to connect to sql server from sas |
|
| In-Reply-To: | <201111041934.pA4GTAip020532@waikiki.cc.uga.edu> |
| Content-Type: | text/plain; charset=ISO-8859-1 |
|---|
usually this job runs in the am, but there was a problem and now I"m trying
to run it again.
I'm thinking the problem could be with XML data type.
does anyone have experience with docxml.value?
select d.xx,
docxml.value
('
(//IsXXX)[3]'
,'varchar(5)'
) as IsXXXAns,
docxml.value
('
(//Name)[3]'
,'varchar(55)'
) as NameAns3,
I have several docxml.value statements in this query.
On Fri, Nov 4, 2011 at 2:34 PM, Tom Abernathy <tom.abernathy@gmail.com>wrote:
> How frequently is it updated? How current do you need the data to be?
> You probably need to setup a scheduled job to pull out a static copy of the
> data for you to analyze. Then you can schedule the pull to run when it
> will
> have less impact on the webpages. 20K records is trivial for a PC to use
> for
> analysis.
>
> On Fri, 4 Nov 2011 14:24:50 -0500, AnnHett <annhett@GMAIL.COM> wrote:
>
> >i'm just getting the columns I want and it's less than 20,000 rows of
> data.
> > I haven't had this problem when I connect to our oracle database, but
> when
> >I use the oracle database that is a reporting copy. This sql server
> >database is the production database that also feeds web pages.
> >
>
|