Error when trying to edit a DTS package - please help

SQL2000 sp2 and sp3a
I'm having trouble getting into DTS design view on a
particular pc. I can get in fine on other pcs. This
apparently started happening just after installing sp3a on
my local machine. The pc I am using can't be rebuilt and
I can't use a different pc. I get a couple of error
messages. After clicking design package, I ge the
following error "Error occurred during creation of a DTS
Package". After clicking ok, I get "The selected package
cannot be opened. The DTS Designer has been closed".
This happens on all packages on all servers (and local)
for the pc I am using. I found one bit of information on
the net, but it didn't help. It was at:
http://www.sqldts.com/default.aspx?228 I then uninstalled
sql and reinstalled. That still didn't work. I've
uninstalled and put sp2, sp3a, different combinations a
few times and still no luck. Has anyone experienced this
or does anyone have any suggestions?
Thanks,
Van JonesThis can happen if the MDAC installation gets corrupted. Since you have
installed SQL Server SP3 then you have MDAC 2.7 SP1. The only way to
correct the MDAC installation would be to install MDAC 2.8 on this server.
Unless this is will cause a problem for you, you can possibly fix the
problem by installing MDAC 2.8.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error when refreshing Taskpad view

When the view of a database in Enterprise Manager has been
set to "Taskpad", and this database is selected, there is
a script error reported the first time. After the error is
issued, you have to change the view to somethinh else
before you can succesfully access the Taskpad view. Does
anybody know how to correct this error?
I recall that being a bug....?
"Wilbert" <anonymous@.discussions.microsoft.com> wrote in message
news:01b101c426a9$aedacd40$3501280a@.phx.gbl...
> When the view of a database in Enterprise Manager has been
> set to "Taskpad", and this database is selected, there is
> a script error reported the first time. After the error is
> issued, you have to change the view to somethinh else
> before you can succesfully access the Taskpad view. Does
> anybody know how to correct this error?
|||I can't seem to find any documentation on it (Knowledge
Base), and I've got SP3a installed.

> I recall that being a bug....?
>
|||It's a bug with Internet Explorer (components of which are used to drive the
Taskpad) rather than SQL Server, so check that you got the latest IE patch.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:173401c426b5$27640960$a301280a@.phx.gbl...
> I can't seem to find any documentation on it (Knowledge
> Base), and I've got SP3a installed.
>
|||I use Windows Server 2003 with IE 6 as a platform. There
are no updates available through Windows Update. Now what?

>--Original Message--
>It's a bug with Internet Explorer (components of which
are used to drive the
>Taskpad) rather than SQL Server, so check that you got
the latest IE patch.
>--
>Jacco Schalkwijk
>SQL Server MVP
|||Its a known bug, which to my knowledge has not been fixed and the workaround
is to select a different view as you have stated. Since it has been around
for such a long time I wouldn't hold your breath about it being fixed
anytime soon.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:1f8001c4276a$fbfec150$a101280a@.phx.gbl...
> I use Windows Server 2003 with IE 6 as a platform. There
> are no updates available through Windows Update. Now what?
>
> are used to drive the
> the latest IE patch.
>

Error when creating a view

Hello,

I'm getting the following error when I try to excute a view against my SQL 7.0 database:

The query processor encountered an unexpected error during execution.

When I click the help button this is what I get:

An ODBC error has been generated. You might have deleted a record that has a foreign key value related to it, or you might have violated a check constraint.

The view I'm trying to create is a query between a table and another view. Here is the other view:

SELECT CSQLocation.Location_ID, CSQMeasure.Measure_ID,
CSQLocation.Location, CSQMeasure.Measure_Name
FROM CSQLocation, CSQMeasure

Here is the view that I'm getting the error on

SELECT ISNULL(CSQObjective.Objective, 0) AS Objective,
vw_getLocationMeasure.Location,
vw_getLocationMeasure.Measure_Name,
vw_getLocationMeasure.Measure_ID
FROM CSQObjective RIGHT OUTER JOIN
vw_getLocationMeasure ON
CSQObjective.Location_ID = vw_getLocationMeasure.Location_ID
AND
CSQObjective.Measure_ID = vw_getLocationMeasure.Measure_ID

Does anyone have any ideas?

Thanks,
RyanWhy you need to use the other view (getLocationMeasure)? It seems the view doesn't add any value. Why don't you just use the two original tables? Just a thought.|||The reason I'm querying a view is because I wasn't able to get the information I was needed with one query and joins. Here is a break down of my db and what I need

MEASURE TABLE
Measure_ID
Measure_Name

LOCATION TABLE
Location_ID
Location

OBJECTIVE TABLE
Objective_ID
Location_ID
Measure_ID
Objective

There are 4 measures, there are about 100 locations, and there is 1 objective per measure per location. Does that make sense? So there will be about 400 obectives in the objective table. What I was trying to do is to return all the Locations, and all the Measures even if there was not and Objective associated with them. If there are no objectives I would like to return a 0, that is where the ISNULL came from. This is the output I would like to have

LOCATION - MEASURE - OBJECTIVE
Chicago - Clean Air - 78.8
Chicago - Clean Water - 75
Chicago - Clean Dumps - 0
Chicago - Clean Roads - 0
Dallas - Clean Air - 90
Dallas - Clean Water - 70
Dallas - Clean Dumps - 25
Dallas - Clean Roads - 0

etc... Does that make sense? With all the joins I've done I have only been able to return the Locations and Measures where there is acutally a value for the Objective. I would like to return 0 if there is no objective.

Thanks
Ryan

Error using EM to view data

Hi,
I have a rather annoying problem with enterprise manager. When I select
Open Table, then Select All Rows . or Select Top . I get the following error
from EM:
Provider cannot be found. It may not be properly installed.
This started a few days ago for no apparent reason. The problem seems to be
limited to my machine, and happens if I access the local data store (MSDE)
or that on other servers (full SQL Sever, ent. ed.). I'm running Win2k
(SP4) and the client tools I'm running are from SQL Server 2000 enterprise
edition (SP3).
All other functions seem to work in EM (such as creating / modifying tables,
etc), and I can access data through other applications on this machine (such
as Query Analyzer, VS.Net, etc).
Things I have tried include reinstalling the latest MDAC (2.8), uninstalling
and reinstalling SQL Server client tools + sp3, and using regsvr32 to
reregister some DLLs suggested in other postings.
One last thing - using Profiler and a different workstation, I noticed that
the Open Table, Select all rows. function starts a new application with a
separate login (the app name is listed as "MS SQLEM - Data Tools"). Does
anyone know anything about this?
TIA for any help anyone can provide.
-DH
I found the solution for this and I am posting it for the common good...
Using filemon and regmon (from sysinternals, nice products), I saw that MMC
was trying to use an old version
of the file msdasql.dll in winnt\system32 rather than the version MDAC
installed in
Program Files\Common Files\System\Ole DB
Using regsvr32 to unregister then re-register the newer file fixed the
problem. Since this file is part of MDAC, I would
have thought that reinsalling MDAC should have fixed the problem, but it
didn't. Ditto for SP4 for Win2k.
I hope this helps someone somewhere someday. -DH
"David Howard" <reply@.to.group> wrote in message
news:UvC8c.290$yN6.61@.newsread2.news.atl.earthlink .net...
> Hi,
> I have a rather annoying problem with enterprise manager. When I select
> Open Table, then Select All Rows . or Select Top . I get the following
error
> from EM:
> Provider cannot be found. It may not be properly installed.
>
> This started a few days ago for no apparent reason. The problem seems to
be
> limited to my machine, and happens if I access the local data store (MSDE)
> or that on other servers (full SQL Sever, ent. ed.). I'm running Win2k
> (SP4) and the client tools I'm running are from SQL Server 2000 enterprise
> edition (SP3).
>
> All other functions seem to work in EM (such as creating / modifying
tables,
> etc), and I can access data through other applications on this machine
(such
> as Query Analyzer, VS.Net, etc).
>
> Things I have tried include reinstalling the latest MDAC (2.8),
uninstalling
> and reinstalling SQL Server client tools + sp3, and using regsvr32 to
> reregister some DLLs suggested in other postings.
>
> One last thing - using Profiler and a different workstation, I noticed
that
> the Open Table, Select all rows. function starts a new application with a
> separate login (the app name is listed as "MS SQLEM - Data Tools"). Does
> anyone know anything about this?
>
> TIA for any help anyone can provide.
> -DH
>
|||It helped me, today.
Thanks a lot for your effort to solve this.
Andrew Arace

Error using EM to view data

Hi,
I have a rather annoying problem with enterprise manager. When I select
Open Table, then Select All Rows . or Select Top . I get the following error
from EM:
Provider cannot be found. It may not be properly installed.
This started a few days ago for no apparent reason. The problem seems to be
limited to my machine, and happens if I access the local data store (MSDE)
or that on other servers (full SQL Sever, ent. ed.). I'm running Win2k
(SP4) and the client tools I'm running are from SQL Server 2000 enterprise
edition (SP3).
All other functions seem to work in EM (such as creating / modifying tables,
etc), and I can access data through other applications on this machine (such
as Query Analyzer, VS.Net, etc).
Things I have tried include reinstalling the latest MDAC (2.8), uninstalling
and reinstalling SQL Server client tools + sp3, and using regsvr32 to
reregister some DLLs suggested in other postings.
One last thing - using Profiler and a different workstation, I noticed that
the Open Table, Select all rows. function starts a new application with a
separate login (the app name is listed as "MS SQLEM - Data Tools"). Does
anyone know anything about this?
TIA for any help anyone can provide.
-DHI found the solution for this and I am posting it for the common good...
Using filemon and regmon (from sysinternals, nice products), I saw that MMC
was trying to use an old version
of the file msdasql.dll in winnt\system32 rather than the version MDAC
installed in
Program Files\Common Files\System\Ole DB
Using regsvr32 to unregister then re-register the newer file fixed the
problem. Since this file is part of MDAC, I would
have thought that reinsalling MDAC should have fixed the problem, but it
didn't. Ditto for SP4 for Win2k.
I hope this helps someone somewhere someday. -DH
"David Howard" <reply@.to.group> wrote in message
news:UvC8c.290$yN6.61@.newsread2.news.atl.earthlink.net...
> Hi,
> I have a rather annoying problem with enterprise manager. When I select
> Open Table, then Select All Rows . or Select Top . I get the following
error
> from EM:
> Provider cannot be found. It may not be properly installed.
>
> This started a few days ago for no apparent reason. The problem seems to
be
> limited to my machine, and happens if I access the local data store (MSDE)
> or that on other servers (full SQL Sever, ent. ed.). I'm running Win2k
> (SP4) and the client tools I'm running are from SQL Server 2000 enterprise
> edition (SP3).
>
> All other functions seem to work in EM (such as creating / modifying
tables,
> etc), and I can access data through other applications on this machine
(such
> as Query Analyzer, VS.Net, etc).
>
> Things I have tried include reinstalling the latest MDAC (2.8),
uninstalling
> and reinstalling SQL Server client tools + sp3, and using regsvr32 to
> reregister some DLLs suggested in other postings.
>
> One last thing - using Profiler and a different workstation, I noticed
that
> the Open Table, Select all rows. function starts a new application with a
> separate login (the app name is listed as "MS SQLEM - Data Tools"). Does
> anyone know anything about this?
>
> TIA for any help anyone can provide.
> -DH
>|||It helped me, today.
Thanks a lot for your effort to solve this.
Andrew Arace

Error Update

Hi,
I create the View which consist of multiple same table. When I want to update via the View, it doesn't allow me to update it, it gave out the following message,
View or function 'Table1' is not updatable because the modification affects multiple base tables.What do you mean by "multiple same table"? If you're saying the view has self-joins, then the view is not going to be updatable.

Error Trying to VIew data in table

When I try to view the data in a table on my SQL SErver 2000 Enterprise
manager, I get the following message
"Provider cannot be found. It may not be properly installed. I have SQL
2000 installed on my PC for the last 8 months and I have had no problems.
All of a sudden I get this
Any helpIMHO, you should view/manipulate your data in SQL Server's Query Analyzer.
At the very least, this will tell you whether the problem is with Enterprise
Manager, or more deeply rooted.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"dfoote" <dfoote@.napcosecurity.com> wrote in message
news:#bRWbQJrEHA.2788@.tk2msftngp13.phx.gbl...
> When I try to view the data in a table on my SQL SErver 2000 Enterprise
> manager, I get the following message
> "Provider cannot be found. It may not be properly installed. I have SQL
> 2000 installed on my PC for the last 8 months and I have had no problems.
> All of a sudden I get this
> Any help
>|||Thanks Aaron
I tried this and I am able to retrieve data via the Query Analyzer. So I
know it is Enterprise manager? Any more suggestion?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eOTc6BLrEHA.2764@.TK2MSFTNGP11.phx.gbl...
> IMHO, you should view/manipulate your data in SQL Server's Query Analyzer.
> At the very least, this will tell you whether the problem is with
> Enterprise
> Manager, or more deeply rooted.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "dfoote" <dfoote@.napcosecurity.com> wrote in message
> news:#bRWbQJrEHA.2788@.tk2msftngp13.phx.gbl...
>> When I try to view the data in a table on my SQL SErver 2000 Enterprise
>> manager, I get the following message
>> "Provider cannot be found. It may not be properly installed. I have SQL
>> 2000 installed on my PC for the last 8 months and I have had no
>> problems.
>> All of a sudden I get this
>> Any help
>>
>|||Have you installed SP3a? Have you updated MDAC recently? If not, have you
considered doing these things?
And have you considered just using Query Analyzer?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"dfoote" <dfoote@.napcosecurity.com> wrote in message
news:uz$P$RLrEHA.3080@.TK2MSFTNGP15.phx.gbl...
> Thanks Aaron
> I tried this and I am able to retrieve data via the Query Analyzer. So I
> know it is Enterprise manager? Any more suggestion?
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:eOTc6BLrEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > IMHO, you should view/manipulate your data in SQL Server's Query
Analyzer.
> > At the very least, this will tell you whether the problem is with
> > Enterprise
> > Manager, or more deeply rooted.
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
> >
> >
> > "dfoote" <dfoote@.napcosecurity.com> wrote in message
> > news:#bRWbQJrEHA.2788@.tk2msftngp13.phx.gbl...
> >> When I try to view the data in a table on my SQL SErver 2000 Enterprise
> >> manager, I get the following message
> >> "Provider cannot be found. It may not be properly installed. I have
SQL
> >> 2000 installed on my PC for the last 8 months and I have had no
> >> problems.
> >> All of a sudden I get this
> >> Any help
> >>
> >>
> >
> >
>

Error Trying to VIew data in table

When I try to view the data in a table on my SQL SErver 2000 Enterprise
manager, I get the following message
"Provider cannot be found. It may not be properly installed. I have SQL
2000 installed on my PC for the last 8 months and I have had no problems.
All of a sudden I get this
Any help
IMHO, you should view/manipulate your data in SQL Server's Query Analyzer.
At the very least, this will tell you whether the problem is with Enterprise
Manager, or more deeply rooted.
http://www.aspfaq.com/
(Reverse address to reply.)
"dfoote" <dfoote@.napcosecurity.com> wrote in message
news:#bRWbQJrEHA.2788@.tk2msftngp13.phx.gbl...
> When I try to view the data in a table on my SQL SErver 2000 Enterprise
> manager, I get the following message
> "Provider cannot be found. It may not be properly installed. I have SQL
> 2000 installed on my PC for the last 8 months and I have had no problems.
> All of a sudden I get this
> Any help
>
|||Thanks Aaron
I tried this and I am able to retrieve data via the Query Analyzer. So I
know it is Enterprise manager? Any more suggestion?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eOTc6BLrEHA.2764@.TK2MSFTNGP11.phx.gbl...
> IMHO, you should view/manipulate your data in SQL Server's Query Analyzer.
> At the very least, this will tell you whether the problem is with
> Enterprise
> Manager, or more deeply rooted.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "dfoote" <dfoote@.napcosecurity.com> wrote in message
> news:#bRWbQJrEHA.2788@.tk2msftngp13.phx.gbl...
>
|||Have you installed SP3a? Have you updated MDAC recently? If not, have you
considered doing these things?
And have you considered just using Query Analyzer?
http://www.aspfaq.com/
(Reverse address to reply.)
"dfoote" <dfoote@.napcosecurity.com> wrote in message
news:uz$P$RLrEHA.3080@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Thanks Aaron
> I tried this and I am able to retrieve data via the Query Analyzer. So I
> know it is Enterprise manager? Any more suggestion?
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:eOTc6BLrEHA.2764@.TK2MSFTNGP11.phx.gbl...
Analyzer.[vbcol=seagreen]
SQL
>

Error Sorting

I need the results of a view sorted by date. When the order by date is added
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
Thanks
Niles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com
|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:

> Niles wrote:
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
David Gugick
Imceda Software
www.imceda.com
|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is added
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maximum
> of 8094"
> Is there a way around this?
> Thanks

Error Sorting

I need the results of a view sorted by date. When the order by date is adde
d
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
ThanksNiles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:

> Niles wrote:
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
David Gugick
Imceda Software
www.imceda.com|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is add
ed
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maxim
um
> of 8094"
> Is there a way around this?
> Thanks

Error Sorting

I need the results of a view sorted by date. When the order by date is added
to the view I get the following error from SQL/ODBC SQL Driver:
"cannot sort a row of size 8813, which is greater than the allowable maximum
of 8094"
Is there a way around this?
ThanksNiles wrote:
> I need the results of a view sorted by date. When the order by date
> is added to the view I get the following error from SQL/ODBC SQL
> Driver: "cannot sort a row of size 8813, which is greater than the
> allowable maximum of 8094"
> Is there a way around this?
> Thanks
You can cut down the result set row size. Why is the row so large?
David Gugick
Imceda Software
www.imceda.com|||I reduced the number of columns returned and it works fine now. Why is the
number of columns a factor here?
Thanks
"David Gugick" wrote:
> Niles wrote:
> > I need the results of a view sorted by date. When the order by date
> > is added to the view I get the following error from SQL/ODBC SQL
> > Driver: "cannot sort a row of size 8813, which is greater than the
> > allowable maximum of 8094"
> > Is there a way around this?
> >
> > Thanks
> You can cut down the result set row size. Why is the row so large?
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Niles wrote:
> I reduced the number of columns returned and it works fine now. Why
> is the number of columns a factor here?
>
8060 is the maximum row size for SQL Server. It's not so much the number
of columns, but the total byte size of all columns in a row. While SQL
Server will allow you to create a table with varchar type columns that
could potentially add up to more than 8060 bytes, you do get a warning
when the table is created. If at any point you change data in a row or
attempt to insert more than 8060 bytes in a row, you get an error.
Since you didn't post any SQL, I can only assume that your table is as
described above, or your columns in the query from multiple tables are
large enough that you're reaching the SQL Server limit.
If you are dealing with a large table or a large table is responsible
for most of the row size, I would encourage you to consider redesigning
the table. Large row sizes mean very low page density. This leads to
excessive page reading on some queries and a general slowdown on the
server when the table is accessed. If you can, you could put some of
that large variable data in a text/ntext column or possibly in another
table.
If you want other suggestions, post your DDL and SQL.
--
David Gugick
Imceda Software
www.imceda.com|||In addition to the other posts:
You could try the ROBUST PLAN optimizer hint.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:D1591C68-5A0E-41A0-A453-C8D7957E5F47@.microsoft.com...
>I need the results of a view sorted by date. When the order by date is added
> to the view I get the following error from SQL/ODBC SQL Driver:
> "cannot sort a row of size 8813, which is greater than the allowable maximum
> of 8094"
> Is there a way around this?
> Thanks