Wednesday, March 21, 2012
msg18452 login failed
after I connect sql I got the message "msg 18452 Login failed for user 'tt'. Reason : not associated with trusted sql server connection"
I should fix the problem, how?? please suggest me...
Thanks ppplease check for your server configuration(in Alias tab, what's network libraries used) in Client Network Utility ! is the server name was correct, if the server configuration
was correct may you check with which user you are connected !
may this help !
4ndr3.
Msg:15335
sp_rename, Line 342
Error: The @.newname value 'BC_SLATFix' is already in use
as a object name and would cause a duplicate that is not
permitted.
Thanks reply
hi,
While using sp_rename stored procedure make sure the value that you are
passing as a new name of the object, does not exists in the database .
Ex:
sp_rename 'old_name,'new_name' --object with the new_name must be existing
in the database.
Vishal Parkar
vgparkar@.yahoo.co.in
sql
Msg 9772 -- Service Broker in database "" cannot be enabled
I backed up a database "Broker", and restored it on the same instance as "BrokerQA" (Broker db still exists, I need them both running on the same instance).
tried sending a few messages, sys.transmissions_queue says: The broker is disabled in the sender's database.
then tried to enable service broker for BrokerQA:
alter database BrokerQA set enable_broker
Msg 9772, Level 16, State 1, Line 2
The Service Broker in database "BrokerQA" cannot be enabled because there is already an enabled Service Broker with the same ID.
Msg 5069, Level 16, State 1, Line 2
ALTER DATABASE statement failed.
How do I reset the service broker ID on the newly restored database?
Thanks!eh, not being lazy does wonders....
alter database viagogoQA set NEW_BROKER
does the trick...
Msg 911, Level 1, State 10, Line 1, Could not locate entry insysdatabases for database
it. I find some blog and follow the instructions, but when I execute
it, I got the Msg 911, Level 1, State 10, Line 1 error
Here is what I did:
C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
\pipe\mssql$microsoft##ssee\sql\query -E
1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
2> to disk = 'd:\sharepoint\config.bak'
3> go
Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
Could not locate entry in sysdatabases for database
'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
No entry found with that name. Make sure that the name is entered
correctly.
Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
Backup log is terminating abnormally.
Can you help? Thanks.
Aaron
Hi
I have never seen the name pipe connection in the server parameter for
SQLCMD but it seems to work!! It would be easier to do something like
np
The error message says that it can find the database in sysdatabases and
that seems to be the issue.
Try
SELECT Name FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
to get the name
John
<achan@.rosewater.com> wrote in message
news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> The SharePoint_config log file is getting too big, I want to shrink
> it. I find some blog and follow the instructions, but when I execute
> it, I got the Msg 911, Level 1, State 10, Line 1 error
> Here is what I did:
> C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> \pipe\mssql$microsoft##ssee\sql\query -E
> 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> 2> to disk = 'd:\sharepoint\config.bak'
> 3> go
> Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> Could not locate entry in sysdatabases for database
> 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> No entry found with that name. Make sure that the name is entered
> correctly.
> Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> Backup log is terminating abnormally.
> Can you help? Thanks.
> Aaron
|||Yes, I use the select name from sysdatabases and it display the name. I also
look into the c:\windows\sysmsi\ssee\mssql.2005\mssql\data where it reside
and the file name is there.
"Tibor Karaszi" wrote:
> The backup command tries to backup a database named
> "SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639". Do you have such database? If not, specify
> the correct database name for the backup command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> <achan@.rosewater.com> wrote in message
> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
>
|||I did that and it did display the file name.
"John Bell" wrote:
> Hi
> I have never seen the name pipe connection in the server parameter for
> SQLCMD but it seems to work!! It would be easier to do something like
> np
> The error message says that it can find the database in sysdatabases and
> that seems to be the issue.
> Try
> SELECT Name FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
> to get the name
> John
>
> <achan@.rosewater.com> wrote in message
> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
>
>
|||Thanks Tibor.
"Tibor Karaszi" wrote:
> Then There's probably something special with the SQL Server that comes with SharePoint (assuming
> that you are 100% positive of the correct database name and that you connected to the correct SQL
> Server instance). You might want to try this in a SharePoint group and see if they have some hints.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Aaron" <Aaron@.discussions.microsoft.com> wrote in message
> news:AC3CD1A0-A462-4398-A560-84842EB40433@.microsoft.com...
>
|||Hi
In which case try
SELECT 'backup log [' + name + '] to disk = ''d:\sharepoint\config.bak''
FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
And the run the command generated in the output.
John
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:005608A7-6260-4D19-BF44-A09A87E4CD90@.microsoft.com...[vbcol=seagreen]
>I did that and it did display the file name.
> "John Bell" wrote:
Msg 911, Level 1, State 10, Line 1, Could not locate entry in
it. I find some blog and follow the instructions, but when I execute
it, I got the Msg 911, Level 1, State 10, Line 1 error
Here is what I did:
C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
\pipe\mssql$microsoft##ssee\sql\query -E
1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
2> to disk = 'd:\sharepoint\config.bak'
3> go
Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
Could not locate entry in sysdatabases for database
'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
No entry found with that name. Make sure that the name is entered
correctly.
Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
Backup log is terminating abnormally.
Can you help? Thanks.
AaronThe backup command tries to backup a database named
"SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639". Do you have such database? If not, specify
the correct database name for the backup command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<achan@.rosewater.com> wrote in message
news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> The SharePoint_config log file is getting too big, I want to shrink
> it. I find some blog and follow the instructions, but when I execute
> it, I got the Msg 911, Level 1, State 10, Line 1 error
> Here is what I did:
> C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> \pipe\mssql$microsoft##ssee\sql\query -E
> 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> 2> to disk = 'd:\sharepoint\config.bak'
> 3> go
> Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> Could not locate entry in sysdatabases for database
> 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> No entry found with that name. Make sure that the name is entered
> correctly.
> Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> Backup log is terminating abnormally.
> Can you help? Thanks.
> Aaron|||Hi
I have never seen the name pipe connection in the server parameter for
SQLCMD but it seems to work!! It would be easier to do something like
np:(local) though!!
The error message says that it can find the database in sysdatabases and
that seems to be the issue.
Try
SELECT Name FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
to get the name
John
<achan@.rosewater.com> wrote in message
news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> The SharePoint_config log file is getting too big, I want to shrink
> it. I find some blog and follow the instructions, but when I execute
> it, I got the Msg 911, Level 1, State 10, Line 1 error
> Here is what I did:
> C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> \pipe\mssql$microsoft##ssee\sql\query -E
> 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> 2> to disk = 'd:\sharepoint\config.bak'
> 3> go
> Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> Could not locate entry in sysdatabases for database
> 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> No entry found with that name. Make sure that the name is entered
> correctly.
> Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> Backup log is terminating abnormally.
> Can you help? Thanks.
> Aaron|||I did that and it did display the file name.
"John Bell" wrote:
> Hi
> I have never seen the name pipe connection in the server parameter for
> SQLCMD but it seems to work!! It would be easier to do something like
> np:(local) though!!
> The error message says that it can find the database in sysdatabases and
> that seems to be the issue.
> Try
> SELECT Name FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
> to get the name
> John
>
> <achan@.rosewater.com> wrote in message
> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> > The SharePoint_config log file is getting too big, I want to shrink
> > it. I find some blog and follow the instructions, but when I execute
> > it, I got the Msg 911, Level 1, State 10, Line 1 error
> >
> > Here is what I did:
> >
> > C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> > \pipe\mssql$microsoft##ssee\sql\query -E
> > 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> > 2> to disk = 'd:\sharepoint\config.bak'
> > 3> go
> > Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> > Could not locate entry in sysdatabases for database
> > 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> > No entry found with that name. Make sure that the name is entered
> > correctly.
> > Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> > Backup log is terminating abnormally.
> >
> > Can you help? Thanks.
> >
> > Aaron
>
>|||Yes, I use the select name from sysdatabases and it display the name. I also
look into the c:\windows\sysmsi\ssee\mssql.2005\mssql\data where it reside
and the file name is there.
"Tibor Karaszi" wrote:
> The backup command tries to backup a database named
> "SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639". Do you have such database? If not, specify
> the correct database name for the backup command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> <achan@.rosewater.com> wrote in message
> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> > The SharePoint_config log file is getting too big, I want to shrink
> > it. I find some blog and follow the instructions, but when I execute
> > it, I got the Msg 911, Level 1, State 10, Line 1 error
> >
> > Here is what I did:
> >
> > C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> > \pipe\mssql$microsoft##ssee\sql\query -E
> > 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> > 2> to disk = 'd:\sharepoint\config.bak'
> > 3> go
> > Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> > Could not locate entry in sysdatabases for database
> > 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> > No entry found with that name. Make sure that the name is entered
> > correctly.
> > Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> > Backup log is terminating abnormally.
> >
> > Can you help? Thanks.
> >
> > Aaron
>|||Then There's probably something special with the SQL Server that comes with SharePoint (assuming
that you are 100% positive of the correct database name and that you connected to the correct SQL
Server instance). You might want to try this in a SharePoint group and see if they have some hints.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:AC3CD1A0-A462-4398-A560-84842EB40433@.microsoft.com...
> Yes, I use the select name from sysdatabases and it display the name. I also
> look into the c:\windows\sysmsi\ssee\mssql.2005\mssql\data where it reside
> and the file name is there.
> "Tibor Karaszi" wrote:
>> The backup command tries to backup a database named
>> "SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639". Do you have such database? If not,
>> specify
>> the correct database name for the backup command.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> <achan@.rosewater.com> wrote in message
>> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
>> > The SharePoint_config log file is getting too big, I want to shrink
>> > it. I find some blog and follow the instructions, but when I execute
>> > it, I got the Msg 911, Level 1, State 10, Line 1 error
>> >
>> > Here is what I did:
>> >
>> > C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
>> > \pipe\mssql$microsoft##ssee\sql\query -E
>> > 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
>> > 2> to disk = 'd:\sharepoint\config.bak'
>> > 3> go
>> > Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
>> > Could not locate entry in sysdatabases for database
>> > 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
>> > No entry found with that name. Make sure that the name is entered
>> > correctly.
>> > Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
>> > Backup log is terminating abnormally.
>> >
>> > Can you help? Thanks.
>> >
>> > Aaron
>>|||Thanks Tibor.
"Tibor Karaszi" wrote:
> Then There's probably something special with the SQL Server that comes with SharePoint (assuming
> that you are 100% positive of the correct database name and that you connected to the correct SQL
> Server instance). You might want to try this in a SharePoint group and see if they have some hints.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Aaron" <Aaron@.discussions.microsoft.com> wrote in message
> news:AC3CD1A0-A462-4398-A560-84842EB40433@.microsoft.com...
> > Yes, I use the select name from sysdatabases and it display the name. I also
> > look into the c:\windows\sysmsi\ssee\mssql.2005\mssql\data where it reside
> > and the file name is there.
> >
> > "Tibor Karaszi" wrote:
> >
> >> The backup command tries to backup a database named
> >> "SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639". Do you have such database? If not,
> >> specify
> >> the correct database name for the backup command.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> <achan@.rosewater.com> wrote in message
> >> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
> >> > The SharePoint_config log file is getting too big, I want to shrink
> >> > it. I find some blog and follow the instructions, but when I execute
> >> > it, I got the Msg 911, Level 1, State 10, Line 1 error
> >> >
> >> > Here is what I did:
> >> >
> >> > C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
> >> > \pipe\mssql$microsoft##ssee\sql\query -E
> >> > 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
> >> > 2> to disk = 'd:\sharepoint\config.bak'
> >> > 3> go
> >> > Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
> >> > Could not locate entry in sysdatabases for database
> >> > 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
> >> > No entry found with that name. Make sure that the name is entered
> >> > correctly.
> >> > Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
> >> > Backup log is terminating abnormally.
> >> >
> >> > Can you help? Thanks.
> >> >
> >> > Aaron
> >>
> >>
>|||Hi
In which case try
SELECT 'backup log [' + name + '] to disk = ''d:\sharepoint\config.bak''
FROM master..sysdatabases where NAME LIKE 'SharePoint_config%'
And the run the command generated in the output.
John
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:005608A7-6260-4D19-BF44-A09A87E4CD90@.microsoft.com...
>I did that and it did display the file name.
> "John Bell" wrote:
>> Hi
>> I have never seen the name pipe connection in the server parameter for
>> SQLCMD but it seems to work!! It would be easier to do something like
>> np:(local) though!!
>> The error message says that it can find the database in sysdatabases and
>> that seems to be the issue.
>> Try
>> SELECT Name FROM master..sysdatabases where NAME LIKE
>> 'SharePoint_config%'
>> to get the name
>> John
>>
>> <achan@.rosewater.com> wrote in message
>> news:3876feb7-df80-4b77-ba38-487da8f57257@.62g2000hsn.googlegroups.com...
>> > The SharePoint_config log file is getting too big, I want to shrink
>> > it. I find some blog and follow the instructions, but when I execute
>> > it, I got the Msg 911, Level 1, State 10, Line 1 error
>> >
>> > Here is what I did:
>> >
>> > C:\Program Files\Microsoft SQL Server\90\tools\binn > sqlcmd -S \\.
>> > \pipe\mssql$microsoft##ssee\sql\query -E
>> > 1> backup log [SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639]
>> > 2> to disk = 'd:\sharepoint\config.bak'
>> > 3> go
>> > Msg 911, Level 1, State 10, Server JITTERBUG\microsoft##ssee, Line 1
>> > Could not locate entry in sysdatabases for database
>> > 'SharePoint_Config_5eb4c0dd-5315-4e4e-8969-10a020979639'
>> > No entry found with that name. Make sure that the name is entered
>> > correctly.
>> > Msg 3013, Level 16, State 1, Server JITTERBUG\microsoft##ssee, Line 1
>> > Backup log is terminating abnormally.
>> >
>> > Can you help? Thanks.
>> >
>> > Aaron
>>
Msg 9002, Level 17, State 4, Line 2
error:
I'm just running a Delete Query using Date Diff function. I read in some
web site that this maybe a problem with SQL Server Management Tools. I
appreciate any help to get around this and any suggestions would be great.
Msg 9002, Level 17, State 4, Line 2
The transaction log for database 'EventSentry' is full. To find out why
space in the log cannot be reused, see the log_reuse_wait_desc column in
sys.databases
Thanks for answering.Fialoa,
Your delete transaction is writting too many log records and filling it up.
If you want to be able to recover then you need to make the log bigger or
make your delete statement work on a smaller subset.
Chris
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||Hi fiaola
SQL Server has to log every data modification operation, every insert,
update and delete. If the log is full, nothing can be written to it and no
data modifications can be done. This has nothing to do with the tool you are
using.
Just do what the messages says. Look at the sys.databases view and tell us
what the log_reuse_wait_desc says. Also look at the recovery model
SELECT log_reuse_wait_desc, recovery_model_desc
FROM sys.databases
WHERE name = 'EventSentry'
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||Thanks for the quick reply, here are the results.
Log_Reuse_Wait_Desc = NOTHING
Recovery_Model_Desc = SIMPLE
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eMohs$WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Hi fiaola
> SQL Server has to log every data modification operation, every insert,
> update and delete. If the log is full, nothing can be written to it and no
> data modifications can be done. This has nothing to do with the tool you
> are using.
> Just do what the messages says. Look at the sys.databases view and tell us
> what the log_reuse_wait_desc says. Also look at the recovery model
> SELECT log_reuse_wait_desc, recovery_model_desc
> FROM sys.databases
> WHERE name = 'EventSentry'
>
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "fiaola" <fiaola@.mail.com> wrote in message
> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in some
>> web site that this maybe a problem with SQL Server Management Tools. I
>> appreciate any help to get around this and any suggestions would be
>> great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>|||It might just be that your log is not big enough for the operation you were
doing.
How big is your log file, and is it set to autogrow?
You can get the information in the sys.files view in the database that is
having the problems.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uH1ss$YUIHA.5816@.TK2MSFTNGP06.phx.gbl...
> Thanks for the quick reply, here are the results.
> Log_Reuse_Wait_Desc = NOTHING
> Recovery_Model_Desc = SIMPLE
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:eMohs$WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Hi fiaola
>> SQL Server has to log every data modification operation, every insert,
>> update and delete. If the log is full, nothing can be written to it and
>> no data modifications can be done. This has nothing to do with the tool
>> you are using.
>> Just do what the messages says. Look at the sys.databases view and tell
>> us what the log_reuse_wait_desc says. Also look at the recovery model
>> SELECT log_reuse_wait_desc, recovery_model_desc
>> FROM sys.databases
>> WHERE name = 'EventSentry'
>>
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||Modify your delete to do it in batches. Pick date ranges that will only
delete 1-5% of the table at once max for each range and then you will
probably be ok.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>|||But we still don't know how big the log is. I've seen logs that are set at
the default 1 MB with no autogrow.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13o71gecmi9nmfb@.corp.supernews.com...
> Modify your delete to do it in batches. Pick date ranges that will only
> delete 1-5% of the table at once max for each range and then you will
> probably be ok.
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "fiaola" <fiaola@.mail.com> wrote in message
> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in some
>> web site that this maybe a problem with SQL Server Management Tools. I
>> appreciate any help to get around this and any suggestions would be
>> great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>|||Problem fixed. Yes, i had to change the query to process less data and i
have set my logs to Autogrow for any future problems.
Thanks for your help. This is a GREAT news group with fast response.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
> But we still don't know how big the log is. I've seen logs that are set at
> the default 1 MB with no autogrow.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||Good point. I haven't seen tlogs set with no autogrow that I recall.
Almost every client I have been at still has the defaults for data/log size
and growths (2MB and 1MB growth for data and 1MB and 10% growth for tlog,
IIRC). Makes me look good when I have them defrag the hard drive and pick
up a big perf gain. :-)
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
> But we still don't know how big the log is. I've seen logs that are set at
> the default 1 MB with no autogrow.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column in
>> sys.databases
>> Thanks for answering.
>>
>>
>|||You're welcome. I'm glad our suggestions helped.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:ubRniqiUIHA.536@.TK2MSFTNGP06.phx.gbl...
> Problem fixed. Yes, i had to change the query to process less data and i
> have set my logs to Autogrow for any future problems.
> Thanks for your help. This is a GREAT news group with fast response.
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column
>> in sys.databases
>> Thanks for answering.
>>
>>
>>
>|||Kevin,
We also try and size our data and log files with limited growth. I have seen
problems with an unlimited log and percent full log alerts.
How much improvement would a disk defrag give you on todays raided disks?
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13o7ttr3dli55fd@.corp.supernews.com...
> Good point. I haven't seen tlogs set with no autogrow that I recall.
> Almost every client I have been at still has the defaults for data/log
> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
> tlog, IIRC). Makes me look good when I have them defrag the hard drive
> and pick up a big perf gain. :-)
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will only
>> delete 1-5% of the table at once max for each range and then you will
>> probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting this
>> error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out why
>> space in the log cannot be reused, see the log_reuse_wait_desc column
>> in sys.databases
>> Thanks for answering.
>>
>>
>>
>|||Limiting your log size is fine, but you should also make sure you have a
good idea of how big it needs to be and then add a generous percentage extra
before setting the upper limit.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Kevin,
> We also try and size our data and log files with limited growth. I have
> seen problems with an unlimited log and percent full log alerts.
> How much improvement would a disk defrag give you on todays raided disks?
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>|||Kalen,
We do that as best we can. We have alerts fired if the data file expands and
then we would look at the log size too. We also would get messages if the
log does get full.
My question is to see how much improvement we might get by defragging.
Thanks
Chris
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:OAAg9h1UIHA.2268@.TK2MSFTNGP02.phx.gbl...
> Limiting your log size is fine, but you should also make sure you have a
> good idea of how big it needs to be and then add a generous percentage
> extra before setting the upper limit.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.InsideSQLServer.com
> http://blog.kalendelaney.com
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>>
>|||I had a client with 300K+ file fragments when I arrived. 18% throughput
improvement from OS file defrag operation. It was on a small RAID10 set (6
drives IIRC).
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> Kevin,
> We also try and size our data and log files with limited growth. I have
> seen problems with an unlimited log and percent full log alerts.
> How much improvement would a disk defrag give you on todays raided disks?
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>|||kevin,
What can we use to see how many file fragments there are? Running W2K3 SP2.
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13od5m2iv7ec365@.corp.supernews.com...
>I had a client with 300K+ file fragments when I arrived. 18% throughput
>improvement from OS file defrag operation. It was on a small RAID10 set (6
>drives IIRC).
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth for
>> tlog, IIRC). Makes me look good when I have them defrag the hard drive
>> and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are set
>> at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> I'm trying to clear some data from a SQL DB table, but i'm getting
>> this error:
>> I'm just running a Delete Query using Date Diff function. I read in
>> some web site that this maybe a problem with SQL Server Management
>> Tools. I appreciate any help to get around this and any suggestions
>> would be great.
>> Msg 9002, Level 17, State 4, Line 2
>> The transaction log for database 'EventSentry' is full. To find out
>> why space in the log cannot be reused, see the log_reuse_wait_desc
>> column in sys.databases
>> Thanks for answering.
>>
>>
>>
>>
>>
>|||Hi Chris
Actually my comment was primarily directly at the OP. You've been around
long enough that I'm sure you've figured out most of the important stuff.
:-)
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:O9J8RU7UIHA.5264@.TK2MSFTNGP02.phx.gbl...
> Kalen,
> We do that as best we can. We have alerts fired if the data file expands
> and then we would look at the log size too. We also would get messages if
> the log does get full.
> My question is to see how much improvement we might get by defragging.
> Thanks
> Chris
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:OAAg9h1UIHA.2268@.TK2MSFTNGP02.phx.gbl...
>> Limiting your log size is fine, but you should also make sure you have a
>> good idea of how big it needs to be and then add a generous percentage
>> extra before setting the upper limit.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read in
>>> some web site that this maybe a problem with SQL Server Management
>>> Tools. I appreciate any help to get around this and any suggestions
>>> would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>
>>
>>
>>
>>
>|||I would recommend diskkeeper. There are many others from symantec,
perfectdisk (raxco maybe?), mcaffee probably has one, one built into windows
(downgraded version of diskkeeper IIRC).
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
> kevin,
> What can we use to see how many file fragments there are? Running W2K3
> SP2.
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>> Modify your delete to do it in batches. Pick date ranges that will
>> only delete 1-5% of the table at once max for each range and then you
>> will probably be ok.
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "fiaola" <fiaola@.mail.com> wrote in message
>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read in
>>> some web site that this maybe a problem with SQL Server Management
>>> Tools. I appreciate any help to get around this and any suggestions
>>> would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>
>>
>>
>>
>>
>|||Last question on this.
Can these products run in a scan mode when SQL is running so we have a
picture of the fragmentation? I am the DBA, the Infrastructure guys do the
Windows maintenance.
Thanks
Chris
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13odvkmn08vcfa0@.corp.supernews.com...
>I would recommend diskkeeper. There are many others from symantec,
>perfectdisk (raxco maybe?), mcaffee probably has one, one built into
>windows (downgraded version of diskkeeper IIRC).
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "Chris Wood" <anonymous@.microsoft.com> wrote in message
> news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
>> kevin,
>> What can we use to see how many file fragments there are? Running W2K3
>> SP2.
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I have
>> seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for data/log
>> size and growths (2MB and 1MB growth for data and 1MB and 10% growth
>> for tlog, IIRC). Makes me look good when I have them defrag the hard
>> drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>> But we still don't know how big the log is. I've seen logs that are
>> set at the default 1 MB with no autogrow.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.InsideSQLServer.com
>> http://blog.kalendelaney.com
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o71gecmi9nmfb@.corp.supernews.com...
>>> Modify your delete to do it in batches. Pick date ranges that will
>>> only delete 1-5% of the table at once max for each range and then
>>> you will probably be ok.
>>>
>>> --
>>> Kevin G. Boles
>>> Indicium Resources, Inc.
>>> SQL Server MVP
>>> kgboles a earthlink dt net
>>>
>>>
>>> "fiaola" <fiaola@.mail.com> wrote in message
>>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read
>>> in some web site that this maybe a problem with SQL Server
>>> Management Tools. I appreciate any help to get around this and any
>>> suggestions would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find out
>>> why space in the log cannot be reused, see the log_reuse_wait_desc
>>> column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>|||I know for a fact that several of them can. I don't know about all of them.
BTW, It is recommended that you shut sql server down during a defrag
operation, but I have at least 2 clients using diskkeeper that do not do
this. Do so at your own risk though.
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"Chris Wood" <anonymous@.microsoft.com> wrote in message
news:uoeWXFHVIHA.5360@.TK2MSFTNGP03.phx.gbl...
> Last question on this.
> Can these products run in a scan mode when SQL is running so we have a
> picture of the fragmentation? I am the DBA, the Infrastructure guys do the
> Windows maintenance.
> Thanks
> Chris
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13odvkmn08vcfa0@.corp.supernews.com...
>>I would recommend diskkeeper. There are many others from symantec,
>>perfectdisk (raxco maybe?), mcaffee probably has one, one built into
>>windows (downgraded version of diskkeeper IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:e6$B%23Y9UIHA.4448@.TK2MSFTNGP03.phx.gbl...
>> kevin,
>> What can we use to see how many file fragments there are? Running W2K3
>> SP2.
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13od5m2iv7ec365@.corp.supernews.com...
>>I had a client with 300K+ file fragments when I arrived. 18% throughput
>>improvement from OS file defrag operation. It was on a small RAID10 set
>>(6 drives IIRC).
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Chris Wood" <anonymous@.microsoft.com> wrote in message
>> news:u0Spi6uUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>> Kevin,
>> We also try and size our data and log files with limited growth. I
>> have seen problems with an unlimited log and percent full log alerts.
>> How much improvement would a disk defrag give you on todays raided
>> disks?
>> Thanks
>> Chris
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13o7ttr3dli55fd@.corp.supernews.com...
>> Good point. I haven't seen tlogs set with no autogrow that I recall.
>> Almost every client I have been at still has the defaults for
>> data/log size and growths (2MB and 1MB growth for data and 1MB and
>> 10% growth for tlog, IIRC). Makes me look good when I have them
>> defrag the hard drive and pick up a big perf gain. :-)
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
>> news:u3AgCjgUIHA.4584@.TK2MSFTNGP03.phx.gbl...
>>> But we still don't know how big the log is. I've seen logs that are
>>> set at the default 1 MB with no autogrow.
>>>
>>> --
>>> HTH
>>> Kalen Delaney, SQL Server MVP
>>> www.InsideSQLServer.com
>>> http://blog.kalendelaney.com
>>>
>>>
>>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>>> news:13o71gecmi9nmfb@.corp.supernews.com...
>>> Modify your delete to do it in batches. Pick date ranges that will
>>> only delete 1-5% of the table at once max for each range and then
>>> you will probably be ok.
>>>
>>> --
>>> Kevin G. Boles
>>> Indicium Resources, Inc.
>>> SQL Server MVP
>>> kgboles a earthlink dt net
>>>
>>>
>>> "fiaola" <fiaola@.mail.com> wrote in message
>>> news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>>> I'm trying to clear some data from a SQL DB table, but i'm getting
>>> this error:
>>> I'm just running a Delete Query using Date Diff function. I read
>>> in some web site that this maybe a problem with SQL Server
>>> Management Tools. I appreciate any help to get around this and
>>> any suggestions would be great.
>>> Msg 9002, Level 17, State 4, Line 2
>>>
>>> The transaction log for database 'EventSentry' is full. To find
>>> out why space in the log cannot be reused, see the
>>> log_reuse_wait_desc column in sys.databases
>>>
>>> Thanks for answering.
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
Msg 9002, Level 17, State 4, Line 2
SQL Server has to log every data modification operation, every insert,
update and delete. If the log is full, nothing can be written to it and no
data modifications can be done. This has nothing to do with the tool you are
using.
Just do what the messages says. Look at the sys.databases view and tell us
what the log_reuse_wait_desc says. Also look at the recovery model
SELECT log_reuse_wait_desc, recovery_model_desc
FROM sys.databases
WHERE name = 'EventSentry'
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uLj2q0WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
> I'm trying to clear some data from a SQL DB table, but i'm getting this
> error:
> I'm just running a Delete Query using Date Diff function. I read in some
> web site that this maybe a problem with SQL Server Management Tools. I
> appreciate any help to get around this and any suggestions would be great.
> Msg 9002, Level 17, State 4, Line 2
> The transaction log for database 'EventSentry' is full. To find out why
> space in the log cannot be reused, see the log_reuse_wait_desc column in
> sys.databases
> Thanks for answering.
>
It might just be that your log is not big enough for the operation you were
doing.
How big is your log file, and is it set to autogrow?
You can get the information in the sys.files view in the database that is
having the problems.
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://blog.kalendelaney.com
"fiaola" <fiaola@.mail.com> wrote in message
news:uH1ss$YUIHA.5816@.TK2MSFTNGP06.phx.gbl...
> Thanks for the quick reply, here are the results.
> Log_Reuse_Wait_Desc = NOTHING
> Recovery_Model_Desc = SIMPLE
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:eMohs$WUIHA.4768@.TK2MSFTNGP02.phx.gbl...
>
sql
Msg 8964 After applying sql server service pack 4
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanks
Hi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
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/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Msg 8964 After applying sql server service pack 4
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
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/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Monday, March 19, 2012
Msg 8964 After applying sql server service pack 4
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
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/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Msg 8621: The query processor ran out of stack space during query optimization
I got the above error when I tried to execute the following query
delete from BUSINESS_ASSOCIATE
where ba_name is null
As you can see the query isn't exactly complicated.
What the table does have is lots of dependancies. I got SSMS to show me all the dependancies and there are literally hundreds (maybe thousands - I'm not going to count them all) of dependant tables and i suspect that is what is causing the problem.
So what do I do about it? This is a valid data-model (industry standard in fact) but SQL won't let me delete data from this table and that's a huge problem for me. Any advice about how to progress would be welcomed.
-Jamie
anyone?
|||
Hi Jamie,
I doubt there's a "quick fix" here, but just out of curiosity, if you set maxdop to 1 for this statement, does it make any difference (assuming you've a multi cpu machine)?
Aside from that there's the obvious workaround of throwing more memory at the server, which I'm sure you've considered anyway.
Cheers
Rob
|||Could you please file a bug at http://connect.microsoft.com/sqlserver with repro script? Can you post the estimated showplan results if the query optimizer can even generate a plan?|||Hi guys,
I sure can. I'll do that from the office tomorrow when I see if the optimiser can produce anything..
-Jamie
|||
Jamie Thomson wrote:
Hi guys,
I sure can. I'll do that from the office tomorrow when I see if the optimiser can produce anything..
-Jamie
OK, its up here: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=227892
Its private though (cos I've uploaded a DB with data in it) so oly MSFT can see it.
-Jamie
|||Thanks for creating the bug and the repro. I assigned it to the right team and I was able to reproduce the problem on a later build also. They will get back to you soon.|||Is the max SQL memory setting too low? If it is fixed, try raising it. Also, I usually leave index creation memory set to 0. Is there a value for that server there?|||This is not related to the memory allocated to SQL Server or any of those settings.|||
Umachandar Jayachandran - MS wrote:
This is not related to the memory allocated to SQL Server or any of those settings.
Thanks Uma. I was just about to go away and test that. Good job I checked here first
-Jamie
|||
It looks like you hit the documented limit on the maximum number of FK references that QP can handle on a single table. It is 253 according to BOL. See below topic:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
|||Was there ever a workaround or a resolution on this?|||There is no workaround other than simplifying your schema to reduce the number of FK references.
Msg 8621: The query processor ran out of stack space during query optimization
I got the above error when I tried to execute the following query
delete from BUSINESS_ASSOCIATE
where ba_name is null
As you can see the query isn't exactly complicated.
What the table does have is lots of dependancies. I got SSMS to show me all the dependancies and there are literally hundreds (maybe thousands - I'm not going to count them all) of dependant tables and i suspect that is what is causing the problem.
So what do I do about it? This is a valid data-model (industry standard in fact) but SQL won't let me delete data from this table and that's a huge problem for me. Any advice about how to progress would be welcomed.
-Jamie
anyone?
|||
Hi Jamie,
I doubt there's a "quick fix" here, but just out of curiosity, if you set maxdop to 1 for this statement, does it make any difference (assuming you've a multi cpu machine)?
Aside from that there's the obvious workaround of throwing more memory at the server, which I'm sure you've considered anyway.
Cheers
Rob
|||Could you please file a bug at http://connect.microsoft.com/sqlserver with repro script? Can you post the estimated showplan results if the query optimizer can even generate a plan?|||Hi guys,
I sure can. I'll do that from the office tomorrow when I see if the optimiser can produce anything..
-Jamie
|||
Jamie Thomson wrote:
Hi guys,
I sure can. I'll do that from the office tomorrow when I see if the optimiser can produce anything..
-Jamie
OK, its up here: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=227892
Its private though (cos I've uploaded a DB with data in it) so oly MSFT can see it.
-Jamie
|||Thanks for creating the bug and the repro. I assigned it to the right team and I was able to reproduce the problem on a later build also. They will get back to you soon.|||Is the max SQL memory setting too low? If it is fixed, try raising it. Also, I usually leave index creation memory set to 0. Is there a value for that server there?|||This is not related to the memory allocated to SQL Server or any of those settings.|||
Umachandar Jayachandran - MS wrote:
This is not related to the memory allocated to SQL Server or any of those settings.
Thanks Uma. I was just about to go away and test that. Good job I checked here first
-Jamie
|||
It looks like you hit the documented limit on the maximum number of FK references that QP can handle on a single table. It is 253 according to BOL. See below topic:
http://msdn2.microsoft.com/en-us/library/ms143432.aspx
|||Was there ever a workaround or a resolution on this?|||There is no workaround other than simplifying your schema to reduce the number of FK references.
msg 8152
Server: Msg 8152, Level 16, State 9, Line 1
String or binary data would be truncated.
The statement has been terminated.
Can anyone please help? Thanks.Hi
It is happening because you try to insert a string value which is greater
then you have declared.
CREATE TABLE #Test
(
col VARCHAR(5)
)
INSERT INTO #Test VALUES ('AAAAAA')--6 characters
" -00Eric Clapton" <a@.b.com> wrote in message
news:Oz1KFHcuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> When I try to run an insert query, I got the following error message:
> Server: Msg 8152, Level 16, State 9, Line 1
> String or binary data would be truncated.
> The statement has been terminated.
>
> Can anyone please help? Thanks.
>|||Hi Eric,
Thanks for the post.
For error message 8152, it usually means when the length of the value
entered by you into a char, varchar, nchar, nvarchar column is longer than
the maximum length of the column. For example, inserting 'FAQ' into a
char(2) column would result in this error.
You cou use Profiler to troubleshooting this error message. Tracing what
statement causes this.
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
msg 8152
Server: Msg 8152, Level 16, State 9, Line 1
String or binary data would be truncated.
The statement has been terminated.
Can anyone please help? Thanks.
Hi
It is happening because you try to insert a string value which is greater
then you have declared.
CREATE TABLE #Test
(
col VARCHAR(5)
)
INSERT INTO #Test VALUES ('AAAAAA')--6 characters
" -00Eric Clapton" <a@.b.com> wrote in message
news:Oz1KFHcuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> When I try to run an insert query, I got the following error message:
> Server: Msg 8152, Level 16, State 9, Line 1
> String or binary data would be truncated.
> The statement has been terminated.
>
> Can anyone please help? Thanks.
>
|||Hi Eric,
Thanks for the post.
For error message 8152, it usually means when the length of the value
entered by you into a char, varchar, nchar, nvarchar column is longer than
the maximum length of the column. For example, inserting 'FAQ' into a
char(2) column would result in this error.
You cou use Profiler to troubleshooting this error message. Tracing what
statement causes this.
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
msg 8152
Server: Msg 8152, Level 16, State 9, Line 1
String or binary data would be truncated.
The statement has been terminated.
Can anyone please help? Thanks.Hi
It is happening because you try to insert a string value which is greater
then you have declared.
CREATE TABLE #Test
(
col VARCHAR(5)
)
INSERT INTO #Test VALUES ('AAAAAA')--6 characters
" -00Eric Clapton" <a@.b.com> wrote in message
news:Oz1KFHcuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> When I try to run an insert query, I got the following error message:
> Server: Msg 8152, Level 16, State 9, Line 1
> String or binary data would be truncated.
> The statement has been terminated.
>
> Can anyone please help? Thanks.
>|||Hi Eric,
Thanks for the post.
For error message 8152, it usually means when the length of the value
entered by you into a char, varchar, nchar, nvarchar column is longer than
the maximum length of the column. For example, inserting 'FAQ' into a
char(2) column would result in this error.
You cou use Profiler to troubleshooting this error message. Tracing what
statement causes this.
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Msg 8127 problem.
I need help with this sql. It works for SQL Server 2000, SP3,
(8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL
',
DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
'CreateTS',
SUM(os.[Lines]) as 'Lines'
FROM aTable os WITH (NOLOCK)
GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
os.[CreateTS]
I am not good at sql, any help is greatly appreciated. The SQL is
dynamically generated by a .Net code and called using OleDb command
class.
Thanks, JoseYou must order by columns in the select list or group by list.
As you say it's not the best SQL as it is generated.
You could:
order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
or
order by min(os.[CreateTS])
or
order by 1,2,3,4
which means order by columns 1,2,3,4 in the select list.
The choice depends on the order you want and in the last case how lazy you
want to be
The syntax on SQL 2005 is generally tighter than 2000. Most people probably
had the odd issue with their code when they tested the upgrade.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...
> Hi,
> I need help with this sql. It works for SQL Server 2000, SP3,
> (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
> SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
> os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYC
OL',
> DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
> 'CreateTS',
> SUM(os.[Lines]) as 'Lines'
> FROM aTable os WITH (NOLOCK)
> GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER B
Y
> os.[CreateTS]
> I am not good at sql, any help is greatly appreciated. The SQL is
> dynamically generated by a .Net code and called using OleDb command
> class.
> Thanks, Jose
>|||Fantastic, that explain the problem. It works.
I end up using the ALIAS:
order by 'CreateTS'
which it seems to work too, and I assume is equivalent to the:
order by min(os.[CreateTS])
one of the versions that you mentioned.
Thank so much,
Jose
Paul Cahill wrote:[vbcol=seagreen]
> You must order by columns in the select list or group by list.
> As you say it's not the best SQL as it is generated.
>
> You could:
> order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
> or
> order by min(os.[CreateTS])
> or
> order by 1,2,3,4
> which means order by columns 1,2,3,4 in the select list.
> The choice depends on the order you want and in the last case how lazy you
> want to be
> The syntax on SQL 2005 is generally tighter than 2000. Most people probabl
y
> had the odd issue with their code when they tested the upgrade.
> Paul
>
>
> "Cuellar" <cuellar1706@.gmail.com> wrote in message
> news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...|||You are welcome.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159977911.674457.60370@.m7g2000cwm.googlegroups.com...
> Fantastic, that explain the problem. It works.
> I end up using the ALIAS:
> order by 'CreateTS'
> which it seems to work too, and I assume is equivalent to the:
> order by min(os.[CreateTS])
> one of the versions that you mentioned.
> Thank so much,
> Jose
> Paul Cahill wrote:
>