Can the TEMPDB be backed up?

You need to run a "Full Backup" on all of your other
Databases.
It may also be a good idea to look at scheduling "Full
Backups" on a more frequent basis. Whenever "Full
Backups" are done, the TempDB is automatically re-sized to
remove all of the temporary data. As TempDB is a system
database, it cannot be manipulated or controlled by any
user.
HTH
Tony C.
>--Original Message--
>Had an alert fire telling me the temdb was full and to
run a backup on it. When I tried it gave me the following
error:
>MIcrosoft SQL_DMO (ODBC SQLSTATE: 42000)
>Backup and Restore operations are not allowed on database
tempdb, BACKUP DATABASE is terminating abnormally.
>HELP!
>
>.
>> Backups" on a more frequent basis. Whenever "Full
> Backups" are done, the TempDB is automatically re-sized to
> remove all of the temporary data.
I don't think that's true. The only "automatic" resizing of tempdb occurs
when SQL Server restarts, where it reverts to its original size.

> As TempDB is a system
> database, it cannot be manipulated or controlled by any
> user.
Also not true. See http://support.microsoft.com/?id=307487 for manual
methods.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Can the TEMPDB be backed up?

You need to run a "Full Backup" on all of your other
Databases.
It may also be a good idea to look at scheduling "Full
Backups" on a more frequent basis. Whenever "Full
Backups" are done, the TempDB is automatically re-sized to
remove all of the temporary data. As TempDB is a system
database, it cannot be manipulated or controlled by any
user.
HTH
Tony C.
>--Original Message--
>Had an alert fire telling me the temdb was full and to
run a backup on it. When I tried it gave me the following
error:
>MIcrosoft SQL_DMO (ODBC SQLSTATE: 42000)
>Backup and Restore operations are not allowed on database
tempdb, BACKUP DATABASE is terminating abnormally.
>HELP!
>
>.
>
> Backups" on a more frequent basis. Whenever "Full
> Backups" are done, the TempDB is automatically re-sized to
> remove all of the temporary data.
I don't think that's true. The only "automatic" resizing of tempdb occurs
when SQL Server restarts, where it reverts to its original size.

> As TempDB is a system
> database, it cannot be manipulated or controlled by any
> user.
Also not true. See http://support.microsoft.com/?id=307487 for manual
methods.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

Can the port change automatically?

We were having problems with our SQL Server so we rebooted
it and when it came back up it was listening on a
different port.
Does anyone have any idea on how this could happen?
Thanks
Kris Bilou
If you specify 0 for the port number in the server network
utility, it will use a dynamic port.
And named instances will use a dynamic port.
-Sue
On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
<kbilou@.suncor.com> wrote:

>We were having problems with our SQL Server so we rebooted
>it and when it came back up it was listening on a
>different port.
>Does anyone have any idea on how this could happen?
>Thanks
>Kris Bilou
|||I understand the dynamic ports but we were using a static
port.
When I shut it down it was using 1245 as it should and was
specified in server newtwork. When I started it back up
it used 1246.
I didn't change it and there were no errors that 1245 was
in use.
[vbcol=seagreen]
>--Original Message--
>If you specify 0 for the port number in the server network
>utility, it will use a dynamic port.
>And named instances will use a dynamic port.
>-Sue
>On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
><kbilou@.suncor.com> wrote:
rebooted
>.
>
|||Dynamic ports. See Sue's post.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Can the port change automatically?

We were having problems with our SQL Server so we rebooted
it and when it came back up it was listening on a
different port.
Does anyone have any idea on how this could happen?
Thanks
Kris BilouIf you specify 0 for the port number in the server network
utility, it will use a dynamic port.
And named instances will use a dynamic port.
-Sue
On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
<kbilou@.suncor.com> wrote:

>We were having problems with our SQL Server so we rebooted
>it and when it came back up it was listening on a
>different port.
>Does anyone have any idea on how this could happen?
>Thanks
>Kris Bilou|||I understand the dynamic ports but we were using a static
port.
When I shut it down it was using 1245 as it should and was
specified in server newtwork. When I started it back up
it used 1246.
I didn't change it and there were no errors that 1245 was
in use.

>--Original Message--
>If you specify 0 for the port number in the server network
>utility, it will use a dynamic port.
>And named instances will use a dynamic port.
>-Sue
>On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
><kbilou@.suncor.com> wrote:
>
rebooted[vbcol=seagreen]
>.
>|||Dynamic ports. See Sue's post.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.