db_owner role

I am getting this error message when disabling a job. The user is not a SA.

TITLE: Microsoft.SqlServer.Smo

Alter failed for Job 'XYZ'.

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

EXECUTE permission denied on object 'sp_help_operator', database 'msdb', owner 'dbo'. (Microsoft SQL Server, Error: 229)

The user can diasble the job if i give db_owner permission on msdb.

Is there a way i can do this without making the user db_owner?

Thanks for any help

There is no specific db_role for job administation, but you can create one. Grant the appropiate permission to the role that you need and assign the user to that role. You sure can also only grant the specific user the rights for that, but the next time you want another user to do the job you will have to repeat your work for that.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks.

Could you describe the "Grant the appropriate permission to the role that you need" in as little more detail as to what has to be done?

Thanks for the help

|||

I don′t know the complete list of permissions you will need for your work to be done, so you would have to go the iterative way to get your work done, here are the steps to complete:

-Create a db Role in the Database msdb (as you want to administer the alerts and things related to the SQL Agent)
-Assign users to this role that should do the administrative work.
-Assign the appropiate permissions to that db role (where the users are currently in) Put in the execute right for that procedure you get an error for.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

DB shrink problem

Hello,

I try to shrink DB, in "Shrink action" I mark "Truncate free space from the
end of file". After press "OK" button I see such a message:

"Error 8985: Could not locate file "file_name.dat" in system.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator."

So, can you tell my what is wrong ? How to resolve this problem ?

Fibre Optic"Fibre Optic" <fibre_optic@.go2.pl> wrote in message
news:cfam4n$nm0$1@.inews.gazeta.pl...
> Hello,
> I try to shrink DB, in "Shrink action" I mark "Truncate free space from
the
> end of file". After press "OK" button I see such a message:
> "Error 8985: Could not locate file "file_name.dat" in system.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator."
> So, can you tell my what is wrong ? How to resolve this problem ?
> Fibre Optic

The error suggests that you have the wrong file name - are you doing this
from Enterprise Manager, or from another tool? You should probably try
shrinking the file directly from Query Analyzer:

http://support.microsoft.com/defaul...8&Product=sql2k

Simon

DB Restore FAIL

In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciated
Regarding the corruption:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or already have database files
with same size as you had when you took the backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com. ..
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level where
> my restore was succesfull. i want to know what i did wrong & why finally it
> succeed after increasing size. any help will be highly appreciated
|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:

> Regarding the corruption:
> http://www.karaszi.com/SQLServer/inf...suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or already have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com. ..
>
|||No. But why did you create the database before the restore. The restore operation does a safety
check. If the database which you are to restore into exists, but the file layout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can create the database for
you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
the restore command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:

> No. But why did you create the database before the restore. The restore operation does a safety
> check. If the database which you are to restore into exists, but the file layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process can create the database for
> you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
>

DB Restore FAIL

In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or already have database files
with same size as you had when you took the backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level where
> my restore was succesfull. i want to know what i did wrong & why finally it
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:
> Regarding the corruption:
> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or already have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> > getting message SUSPECT.
> >
> > So i created new DB with initial size of 5GB to try to restore 50GB the
> > original DB & it failed.
> >
> > Finally i was able to restore, by increasing size to substantial level where
> > my restore was succesfull. i want to know what i did wrong & why finally it
> > succeed after increasing size. any help will be highly appreciated
>|||No. But why did you create the database before the restore. The restore operation does a safety
check. If the database which you are to restore into exists, but the file layout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can create the database for
you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
the restore command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>> Regarding the corruption:
>> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> As for restore:
>> You cannot restore into a smaller database. SQL Server need to create or already have database
>> files
>> with same size as you had when you took the backup.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
>> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
>> > getting message SUSPECT.
>> >
>> > So i created new DB with initial size of 5GB to try to restore 50GB the
>> > original DB & it failed.
>> >
>> > Finally i was able to restore, by increasing size to substantial level where
>> > my restore was succesfull. i want to know what i did wrong & why finally it
>> > succeed after increasing size. any help will be highly appreciated
>>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:
> No. But why did you create the database before the restore. The restore operation does a safety
> check. If the database which you are to restore into exists, but the file layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process can create the database for
> you when you perform the restore operation, it doesn't have to exist. Or, use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
> > Hi Tibor,
> >
> > Will an autogrow option in 5GB DB work in this scenario?
> >
> > Thanks,
> > Sree
> >
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> Regarding the corruption:
> >> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> As for restore:
> >> You cannot restore into a smaller database. SQL Server need to create or already have database
> >> files
> >> with same size as you had when you took the backup.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ureader.com...
> >> > In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> >> > getting message SUSPECT.
> >> >
> >> > So i created new DB with initial size of 5GB to try to restore 50GB the
> >> > original DB & it failed.
> >> >
> >> > Finally i was able to restore, by increasing size to substantial level where
> >> > my restore was succesfull. i want to know what i did wrong & why finally it
> >> > succeed after increasing size. any help will be highly appreciated
> >>
> >>
>

DB Restore FAIL

In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
getting message SUSPECT.
So i created new DB with initial size of 5GB to try to restore 50GB the
original DB & it failed.
Finally i was able to restore, by increasing size to substantial level where
my restore was succesfull. i want to know what i did wrong & why finally it
succeed after increasing size. any help will be highly appreciatedRegarding the corruption:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
As for restore:
You cannot restore into a smaller database. SQL Server need to create or alr
eady have database files
with same size as you had when you took the backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94be4@.ur
eader.com...

> In my SQL SERVER 2000, my Database(DB) say for e.g. XYZ got corrupted
> getting message SUSPECT.
> So i created new DB with initial size of 5GB to try to restore 50GB the
> original DB & it failed.
> Finally i was able to restore, by increasing size to substantial level whe
re
> my restore was succesfull. i want to know what i did wrong & why finally i
t
> succeed after increasing size. any help will be highly appreciated|||Hi Tibor,
Will an autogrow option in 5GB DB work in this scenario?
Thanks,
Sree
"Tibor Karaszi" wrote:

> Regarding the corruption:
> http://www.karaszi.com/SQLServer/in..._suspect_db.asp
> As for restore:
> You cannot restore into a smaller database. SQL Server need to create or a
lready have database files
> with same size as you had when you took the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Jay" <sqldba@.abc.com> wrote in message news:fa00ab1c82794850b98da6a02af94
be4@.ureader.com...
>|||No. But why did you create the database before the restore. The restore oper
ation does a safety
check. If the database which you are to restore into exists, but the file la
yout doesn't match, you
get an error. This is so you don't do a mistake. But the restore process can
create the database for
you when you perform the restore operation, it doesn't have to exist. Or, us
e the REPLACE option of
the restore command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...[vbcol=seagreen]
> Hi Tibor,
> Will an autogrow option in 5GB DB work in this scenario?
> Thanks,
> Sree
>
> "Tibor Karaszi" wrote:
>|||Ya thats correct, but still didnt try this option yet thats why.
Thanks, Tibor.
"Tibor Karaszi" wrote:

> No. But why did you create the database before the restore. The restore op
eration does a safety
> check. If the database which you are to restore into exists, but the file
layout doesn't match, you
> get an error. This is so you don't do a mistake. But the restore process c
an create the database for
> you when you perform the restore operation, it doesn't have to exist. Or,
use the REPLACE option of
> the restore command.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
> news:2C05DE26-DD1A-429F-A8CF-8997481C4B81@.microsoft.com...
>

DB Restore

Hi,
I am restoring a DB from osql command line and I am getting following
message at the end of the resotration. I couldn't understand first two
lines. I searched BOL but couldn't find anything.. anyone know what is
the _dat file? and why it was created? I can see that DB was restored
succesfully. Just puzzlling by these two lines...
Processed 1816 pages for database 'mydb_oltp', file 'mydbtemp_dat' on
file 1.
Processed 1 pages for database 'mydb_oltp', file 'mydbtemp_log' on file
1.
RESTORE DATABASE successfully processed 1817 pages in 12.770 seconds
(1.165
MB/sec).
Thank you,
hjHitesh wrote:
> Hi,
> I am restoring a DB from osql command line and I am getting following
> message at the end of the resotration. I couldn't understand first two
> lines. I searched BOL but couldn't find anything.. anyone know what is
> the _dat file? and why it was created? I can see that DB was restored
> succesfully. Just puzzlling by these two lines...
> Processed 1816 pages for database 'mydb_oltp', file 'mydbtemp_dat' on
> file 1.
> Processed 1 pages for database 'mydb_oltp', file 'mydbtemp_log' on file
> 1.
> RESTORE DATABASE successfully processed 1817 pages in 12.770 seconds
> (1.165
> MB/sec).
> Thank you,
> hj
>
First of all, these are NOT error messages, they are simply status
messages. A SQL Server database consists of, at minimum, two physical
files - a data file (.MDF) and a transaction log file (.LDF). Each
physical file is associated with a "logical" internal file within the
database. These messages you see are telling you that the logical files
"mydbtemp_dat" and "mydbtemp_log" were created successfully.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I thought it creates MDF and LDF as the name of the database i.e.
mydb_oltp.mdf and mydb_oltp.ldf. I do not have another instance running
on this server that has logical or physical files name like that.. so I
was kind of puzzled why it created temp names.
Thank you anyway,
hj
Tracy McKibben wrote:
> Hitesh wrote:
> > Hi,
> > I am restoring a DB from osql command line and I am getting following
> > message at the end of the resotration. I couldn't understand first two
> > lines. I searched BOL but couldn't find anything.. anyone know what is
> > the _dat file? and why it was created? I can see that DB was restored
> > succesfully. Just puzzlling by these two lines...
> >
> > Processed 1816 pages for database 'mydb_oltp', file 'mydbtemp_dat' on
> > file 1.
> > Processed 1 pages for database 'mydb_oltp', file 'mydbtemp_log' on file
> > 1.
> > RESTORE DATABASE successfully processed 1817 pages in 12.770 seconds
> > (1.165
> > MB/sec).
> >
> > Thank you,
> > hj
> >
> First of all, these are NOT error messages, they are simply status
> messages. A SQL Server database consists of, at minimum, two physical
> files - a data file (.MDF) and a transaction log file (.LDF). Each
> physical file is associated with a "logical" internal file within the
> database. These messages you see are telling you that the logical files
> "mydbtemp_dat" and "mydbtemp_log" were created successfully.
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||The database that was backed up has logical file names like
that - nothing in the restore process created temp file
names. The mdf and ldf files are physical files. As Tracy
already pointed out, mydbtemp_dat and mydbtemp_log are the
logical file names. mydb_oltp.mdf and mydb_oltp.ldf are the
physical files. The restore will restore by default with the
same logical and physical file names that the backed up
database used. You can see both the physical file names and
the logical file names by executing the following in query
analyzer or osql:
use mydb_oltp
go
exec sp_helpfile
In the result set, name is the logical file name and
filename is the physical file name.
-Sue
On 8 Aug 2006 06:06:23 -0700, "Hitesh" <hitesh287@.gmail.com>
wrote:
>I thought it creates MDF and LDF as the name of the database i.e.
>mydb_oltp.mdf and mydb_oltp.ldf. I do not have another instance running
>on this server that has logical or physical files name like that.. so I
>was kind of puzzled why it created temp names.
>Thank you anyway,
>hj
>
>Tracy McKibben wrote:
>> Hitesh wrote:
>> > Hi,
>> > I am restoring a DB from osql command line and I am getting following
>> > message at the end of the resotration. I couldn't understand first two
>> > lines. I searched BOL but couldn't find anything.. anyone know what is
>> > the _dat file? and why it was created? I can see that DB was restored
>> > succesfully. Just puzzlling by these two lines...
>> >
>> > Processed 1816 pages for database 'mydb_oltp', file 'mydbtemp_dat' on
>> > file 1.
>> > Processed 1 pages for database 'mydb_oltp', file 'mydbtemp_log' on file
>> > 1.
>> > RESTORE DATABASE successfully processed 1817 pages in 12.770 seconds
>> > (1.165
>> > MB/sec).
>> >
>> > Thank you,
>> > hj
>> >
>> First of all, these are NOT error messages, they are simply status
>> messages. A SQL Server database consists of, at minimum, two physical
>> files - a data file (.MDF) and a transaction log file (.LDF). Each
>> physical file is associated with a "logical" internal file within the
>> database. These messages you see are telling you that the logical files
>> "mydbtemp_dat" and "mydbtemp_log" were created successfully.
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com

DB Process is dead or not enabled

Hi,
I am getting the following SQL Server message in my client application after
processing volume of transaction.
Error Message
=========
10005,-1, DB Process is dead or not enabled
SQL Server Edition
============
MSDE with SP3
OS Edition
=======
Windows 2000 ProfessionalHi
Any other errors in the SQL errorlog?
"Balaji Prabhu.T" <anonymous@.discussions.microsoft.com> wrote in message
news:4972B017-04B1-451B-A8D2-D88DAF325863@.microsoft.com...
> Hi,
> I am getting the following SQL Server message in my client application
after processing volume of transaction.
> Error Message
> =========
> 10005,-1, DB Process is dead or not enabled
> SQL Server Edition
> ============
> MSDE with SP3
> OS Edition
> =======
> Windows 2000 Professional
>

DB Library error: Login incorrect

I have application that I received the error listed below from SQL Server
2000 database.
Please help me resolve this error message.
Thank You,
Error source: dbopen
DB Library error: Login incorrect
SQL Server message: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.try:
http://support.microsoft.com/kb/827422
-oj
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:12208B72-C604-4314-AF3C-57579401DABC@.microsoft.com...
> I have application that I received the error listed below from SQL Server
> 2000 database.
> Please help me resolve this error message.
> Thank You,
>
> Error source: dbopen
> DB Library error: Login incorrect
> SQL Server message: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>

DB Library error: Login incorrect

I have application that I received the error listed below from SQL Server
2000 database.
Please help me resolve this error message.
Thank You,
Error source: dbopen
DB Library error: Login incorrect
SQL Server message: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.try:
http://support.microsoft.com/kb/827422
-oj
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:12208B72-C604-4314-AF3C-57579401DABC@.microsoft.com...
> I have application that I received the error listed below from SQL Server
> 2000 database.
> Please help me resolve this error message.
> Thank You,
>
> Error source: dbopen
> DB Library error: Login incorrect
> SQL Server message: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
>

db library error ?

Hi,
the application that I run has crashed this morning when
the following error message apeared :
SQL Server message 10054:
Possible network Error: Write to SQL Server failed.
General network error.Chek your documentation.
Debuging info:DBsqlexec, Begin Transaction - execute DBproc
optional info : Begin transaction.
At the same time the following appeared in SQl Server
Error log :
The log file for database 'tempdb' is full. Back up the
transaction log for the database to free up some log
space..
Error: 9002, Severity: 17, State: 6
Does anybody know what caused it?
I was reading something about error handling db library
error messages ...does this error handling should be
incorporated in the application ?
Why am I seeing "The log file for database 'tempdb' is
full" . As far as I know temp db should never be full and
as long as I have space for it's expansion there should be
no problem.
Thanks very much,
Natasa
Sometimes autogrow doesn't grow fast enough for the workers that need the space. Try pre-allocating
space for the tempdb database files...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Natasha" <anonymous@.discussions.microsoft.com> wrote in message
news:084e01c50df8$810d2520$a601280a@.phx.gbl...
> Hi,
> the application that I run has crashed this morning when
> the following error message apeared :
> SQL Server message 10054:
> Possible network Error: Write to SQL Server failed.
> General network error.Chek your documentation.
> Debuging info:DBsqlexec, Begin Transaction - execute DBproc
> optional info : Begin transaction.
> At the same time the following appeared in SQl Server
> Error log :
> The log file for database 'tempdb' is full. Back up the
> transaction log for the database to free up some log
> space..
> Error: 9002, Severity: 17, State: 6
> Does anybody know what caused it?
> I was reading something about error handling db library
> error messages ...does this error handling should be
> incorporated in the application ?
> Why am I seeing "The log file for database 'tempdb' is
> full" . As far as I know temp db should never be full and
> as long as I have space for it's expansion there should be
> no problem.
> Thanks very much,
> Natasa
>

db library error ?

Hi,
the application that I run has crashed this morning when
the following error message apeared :
SQL Server message 10054:
Possible network Error: Write to SQL Server failed.
General network error.Chek your documentation.
Debuging info:DBsqlexec, Begin Transaction - execute DBproc
optional info : Begin transaction.
At the same time the following appeared in SQl Server
Error log :
The log file for database 'tempdb' is full. Back up the
transaction log for the database to free up some log
space..
Error: 9002, Severity: 17, State: 6
Does anybody know what caused it?
I was reading something about error handling db library
error messages ...does this error handling should be
incorporated in the application ?
Why am I seeing "The log file for database 'tempdb' is
full" . As far as I know temp db should never be full and
as long as I have space for it's expansion there should be
no problem.
Thanks very much,
NatasaSometimes autogrow doesn't grow fast enough for the workers that need the sp
ace. Try pre-allocating
space for the tempdb database files...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Natasha" <anonymous@.discussions.microsoft.com> wrote in message
news:084e01c50df8$810d2520$a601280a@.phx.gbl...
> Hi,
> the application that I run has crashed this morning when
> the following error message apeared :
> SQL Server message 10054:
> Possible network Error: Write to SQL Server failed.
> General network error.Chek your documentation.
> Debuging info:DBsqlexec, Begin Transaction - execute DBproc
> optional info : Begin transaction.
> At the same time the following appeared in SQl Server
> Error log :
> The log file for database 'tempdb' is full. Back up the
> transaction log for the database to free up some log
> space..
> Error: 9002, Severity: 17, State: 6
> Does anybody know what caused it?
> I was reading something about error handling db library
> error messages ...does this error handling should be
> incorporated in the application ?
> Why am I seeing "The log file for database 'tempdb' is
> full" . As far as I know temp db should never be full and
> as long as I have space for it's expansion there should be
> no problem.
> Thanks very much,
> Natasa
>

db library error ?

Hi,
the application that I run has crashed this morning when
the following error message apeared :
SQL Server message 10054:
Possible network Error: Write to SQL Server failed.
General network error.Chek your documentation.
Debuging info:DBsqlexec, Begin Transaction - execute DBproc
optional info : Begin transaction.
At the same time the following appeared in SQl Server
Error log :
The log file for database 'tempdb' is full. Back up the
transaction log for the database to free up some log
space..
Error: 9002, Severity: 17, State: 6
Does anybody know what caused it?
I was reading something about error handling db library
error messages ...does this error handling should be
incorporated in the application ?
Why am I seeing "The log file for database 'tempdb' is
full" . As far as I know temp db should never be full and
as long as I have space for it's expansion there should be
no problem.
Thanks very much,
NatasaSometimes autogrow doesn't grow fast enough for the workers that need the space. Try pre-allocating
space for the tempdb database files...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Natasha" <anonymous@.discussions.microsoft.com> wrote in message
news:084e01c50df8$810d2520$a601280a@.phx.gbl...
> Hi,
> the application that I run has crashed this morning when
> the following error message apeared :
> SQL Server message 10054:
> Possible network Error: Write to SQL Server failed.
> General network error.Chek your documentation.
> Debuging info:DBsqlexec, Begin Transaction - execute DBproc
> optional info : Begin transaction.
> At the same time the following appeared in SQl Server
> Error log :
> The log file for database 'tempdb' is full. Back up the
> transaction log for the database to free up some log
> space..
> Error: 9002, Severity: 17, State: 6
> Does anybody know what caused it?
> I was reading something about error handling db library
> error messages ...does this error handling should be
> incorporated in the application ?
> Why am I seeing "The log file for database 'tempdb' is
> full" . As far as I know temp db should never be full and
> as long as I have space for it's expansion there should be
> no problem.
> Thanks very much,
> Natasa
>

db Full auto-notification

Hi everybody,

Is it possible to make an alert on MSSQL so that the Administrator is automatically notified (by email or net message for instance) when one of the db comes full, or when the free space goes under a critical level ?

Is the "available space" for each database stored in some table of the Master database ?

many thanks in advance for your help ;-)Go thru books online on setting ALERTS and use ERROR 1105 to inform the status of the database size if its full by 90%.