errorlog

I have SQL 2000 with sp3. I can't recycle the errorlog. I have already
tried sp_cycle_errorlog and it does not do it. The errorlog is up to
300 MB. Any suggestions short of stopping/starting SQL ?
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!Raziq Shekha wrote:
> I have SQL 2000 with sp3. I can't recycle the errorlog. I have
> already tried sp_cycle_errorlog and it does not do it. The errorlog
> is up to 300 MB. Any suggestions short of stopping/starting SQL ?
Have you tried DBCC ERRORLOG?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks Sebastian, yes I have already tried dbcc errorlog it is also not
working. Any other ideas?
Raziq.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Raziq Shekha wrote:
> Thanks Sebastian, yes I have already tried dbcc errorlog it is also
> not working. Any other ideas?
No idea. It should be immediate. Do you check your file size in Explorer or
SQL EM?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Raziq Shekha wrote:
> I have SQL 2000 with sp3. I can't recycle the errorlog. I have
> already tried sp_cycle_errorlog and it does not do it. The errorlog
> is up to 300 MB. Any suggestions short of stopping/starting SQL ?
Ensure that your ERRORLOG.* files do _not_ have read only attribute set.
Markku

errorlog

I have SQL 2000 with sp3. I can't recycle the errorlog. I have already
tried sp_cycle_errorlog and it does not do it. The errorlog is up to
300 MB. Any suggestions short of stopping/starting SQL ?
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Raziq Shekha wrote:
> I have SQL 2000 with sp3. I can't recycle the errorlog. I have
> already tried sp_cycle_errorlog and it does not do it. The errorlog
> is up to 300 MB. Any suggestions short of stopping/starting SQL ?
Have you tried DBCC ERRORLOG?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Error: The index entry exceeds the maximum length of 900 bytes

Hi,
while trying to insert I get the error msg. (despite of Microsoft SQL Server
2000 sp3)
"Server: Msg 1946, Level 16, State 4, Line 3
Operation failed. The index entry of length 986 bytes for the index
'IndexName' exceeds the maximum length of 900 bytes."
http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
The number of entries is about 11400, last id = 11889.
Any ideas? What is a temporary index? Is it possible to extend this limit?
Regards,
BerndBernd,
I suspect you have a varying column (n/varchar or varbinary) indexed. While
you can add these to an index, index rows cannot exceed 900 bytes.
Therefore, if the combined datalength of all columns in your insert that are
included in a single index is > 900, the insert will fail. Try the
following example to see what I mean:
CREATE TABLE #IndexTest(ColA INT, ColB VARCHAR(1000))
GO
CREATE INDEX VARCHARINDEX ON #IndexTest(ColB)
Go
INSERT #IndexTest VALUES (1, REPLICATE('0', 900))
INSERT #IndexTest VALUES (2, REPLICATE('0', 901))
GO
SELECT * FROM #IndexTest
GO
"Bernd Binder" <bernd@.binders.de> wrote in message
news:udocFIRkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> Hi,
> while trying to insert I get the error msg. (despite of Microsoft SQL
Server
> 2000 sp3)
> "Server: Msg 1946, Level 16, State 4, Line 3
> Operation failed. The index entry of length 986 bytes for the index
> 'IndexName' exceeds the maximum length of 900 bytes."
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> The number of entries is about 11400, last id = 11889.
> Any ideas? What is a temporary index? Is it possible to extend this limit?
> Regards,
> Bernd
>|||FYI - In SQL Server 2005 this restriction is lifted - kind of. The total
length of all key columns in an index cannot exceed 900 bytes but using the
new INCLUDE syntax, you can add extra columns of any length to an index
record - thus creating a query covering index.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> wrote in message
news:e3NOaiRkEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Bernd,
> I suspect you have a varying column (n/varchar or varbinary) indexed.
While
> you can add these to an index, index rows cannot exceed 900 bytes.
> Therefore, if the combined datalength of all columns in your insert that
are
> included in a single index is > 900, the insert will fail. Try the
> following example to see what I mean:
>
> CREATE TABLE #IndexTest(ColA INT, ColB VARCHAR(1000))
> GO
> CREATE INDEX VARCHARINDEX ON #IndexTest(ColB)
> Go
> INSERT #IndexTest VALUES (1, REPLICATE('0', 900))
> INSERT #IndexTest VALUES (2, REPLICATE('0', 901))
> GO
> SELECT * FROM #IndexTest
> GO
>
> "Bernd Binder" <bernd@.binders.de> wrote in message
> news:udocFIRkEHA.1348@.TK2MSFTNGP15.phx.gbl...
> > Hi,
> >
> > while trying to insert I get the error msg. (despite of Microsoft SQL
> Server
> > 2000 sp3)
> >
> > "Server: Msg 1946, Level 16, State 4, Line 3
> > Operation failed. The index entry of length 986 bytes for the index
> > 'IndexName' exceeds the maximum length of 900 bytes."
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> >
> > The number of entries is about 11400, last id = 11889.
> >
> > Any ideas? What is a temporary index? Is it possible to extend this
limit?
> >
> > Regards,
> > Bernd
> >
> >
>|||"Adam Machanic" <amachanic@.hotmail._removetoemail_.com> schrieb im
Newsbeitrag news:e3NOaiRkEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Bernd,
> I suspect you have a varying column (n/varchar or varbinary) indexed.
While
Yes.
Thank you.
[...]
> >
> > "Server: Msg 1946, Level 16, State 4, Line 3
> > Operation failed. The index entry of length 986 bytes for the index
> > 'IndexName' exceeds the maximum length of 900 bytes."
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;280744
> >
> > The number of entries is about 11400, last id = 11889.
> >
> > Any ideas? What is a temporary index? Is it possible to extend this
limit?
> >
> > Regards,
> > Bernd
> >
> >
>

ERROR: table don't support this operation

hello all,

this query causes error on some servers (sql2000 sp3). on our development server is this ok. we have restore the database from customer server to the development server, this is ok too. we don't know which configuration on the server can change to solve the problem.
-
select distinct V.Vereinsname as Vereinsname, V.VNr as VerNr, V.PLZ as PLZ, V.Ort as Ort, V.Strasse1 as Stra?e1, V.Strasse2 as Stra?e2, '0' as Sel
, V.Statusfeld01, V.Statusfeld02, V.Statusfeld03, V.Statusfeld04, V.Statusfeld05, V.Statusfeld06, V.Statusfeld07, V.Statusfeld08, V.Statusfeld09
, V.Statusfeld10, V.Statusfeld11, V.Statusfeld12, V.Statusfeld13, V.Statusfeld14, V.Statusfeld15, V.Statusfeld16

from VRMWSTD V
where 0 < V.VKrNr
and V.VKrNr in (1)
order by Vereinsname

-
the message in german is: "Tabelle unterstützt diese Operation nicht."

many thanks in advance

duong

Have you checked the index?|||just a question but why do you do this -
where 0 < V.VKrNr
and V.VKrNr in (1)

and not simply

where V.VKrNr = 1

I don't know. . . sql might optimize it out, but seems like overkill.|||Could you please post a simple repro script? The error message looks like a client library message and not SQL Server. It could be that you are trying to add/update rows in the datatable or recordset for example and it is not supported. This can be due to the nature of the SELECT statement (use of DISTINCT and ORDER BY clauses) which will make the resultset read-only.