Live Webcast tomorrow Essential Team System for Database Developers

Live Webcast tomorrow

Essential Team System for Database Developers

1 PM Central time 12/28

https://www.clicktoattend.com/invitation.aspx?code=112602

Do we know if there will be any SSIS topics covered in this Webcast?|||I don't know, but I thought it would be of general interest and on another thread someone was asking about test data generation and that will be covered.

Live Streaming Requirements?

We’re doing a website for a TV station, and they want to have a live TV broadcast on their website, our experience is basically in CMS and portal solutions, but we never had any experience in live streaming, so this is all new to us, so we’re looking for a technical and financial proposal with your suggestions and recommendations, this is the details of the project with some of the inquiries we have:

-The signal is SDI (Pal 25 fps)

-The output (online streaming) 15 fps

-The user will have two options to view the movie in:

1. Low: 56K

2. High: 300K

-The video should come within a customized designed page, probably as a code we can place inside an html table’s cell, not as a link for external link

-We’re expecting about 200 users for the video each month; each user’s logon time expected 10 min.

-We have a Red hat Linux on our server that will host the site, and we use php/MySql technology.

Inquires:

1. Why Windows media is better then Real in terms of performance, can you provide us with a comparison table to include it to our client?

2. If we choose Windows media, what are the requirements we need to have, form both; the TV station side, and in our Linux server? And how much would it cost?

4. Is there any hardware required from the TV station side such as DVR, or some sort of encoder, if so; what’s you’re recommendations (type/ brand), please note that this is a TV station and it needs a high quality professional hardware

5. How (and this is probably the most ambiguous task)

5.1. Do you broadcast the digital signal coming from the encoder (I guess) to the server?

5.2. And then place this signal on a PHP page? Do you give us a link to embed in our code?

6. If we choose to host the live streaming on a separated server and include the URL in our code, would that still required from our server to support Windows media, or it doesn’t matter as long as the video streaming is hosted on a Windows streaming server

7. How much disk space does it need to host a live streaming (with the details mentioned above)?

We would really appreciate your comments and suggestions, as this is our 1^st time to dealing with live streaming.

Check informedia.tv, get in touch with someone there to help you setup a test pilot.sql

Live Streaming Requirements?

We’re doing a website for a TV station, and they want to have a live TV broadcast on their website, our experience is basically in CMS and portal solutions, but we never had any experience in live streaming, so this is all new to us, so we’re looking for a technical and financial proposal with your suggestions and recommendations, this is the details of the project with some of the inquiries we have:

-The signal is SDI (Pal 25 fps)

-The output (online streaming) 15 fps

-The user will have two options to view the movie in:

1. Low: 56K

2. High: 300K

-The video should come within a customized designed page, probably as a code we can place inside an html table’s cell, not as a link for external link

-We’re expecting about 200 users for the video each month; each user’s logon time expected 10 min.

-We have a Red hat Linux on our server that will host the site, and we use php/MySql technology.

Inquires:

1. Why Windows media is better then Real in terms of performance, can you provide us with a comparison table to include it to our client?

2. If we choose Windows media, what are the requirements we need to have, form both; the TV station side, and in our Linux server? And how much would it cost?

4. Is there any hardware required from the TV station side such as DVR, or some sort of encoder, if so; what’s you’re recommendations (type/ brand), please note that this is a TV station and it needs a high quality professional hardware

5. How (and this is probably the most ambiguous task)

5.1. Do you broadcast the digital signal coming from the encoder (I guess) to the server?

5.2. And then place this signal on a PHP page? Do you give us a link to embed in our code?

6. If we choose to host the live streaming on a separated server and include the URL in our code, would that still required from our server to support Windows media, or it doesn’t matter as long as the video streaming is hosted on a Windows streaming server

7. How much disk space does it need to host a live streaming (with the details mentioned above)?

We would really appreciate your comments and suggestions, as this is our 1^st time to dealing with live streaming.

Check informedia.tv, get in touch with someone there to help you setup a test pilot.

Live server running out of space - Can't reduce Transaction Log!

Hi,
I have just come across a bit of a problem of my Windows 200 server running
SQL Server 2000....I am running out of space!
I have aout 2GB left. I have know this for some time, and for technical
reasons just found out I can't add a new disk...but that's another story.
I have looked at what I can reduce to increase the space, and it seems one
of the smaller database I have on the server, i.e. 16MB, has a log file of
4.8GB!
I am not sure why this has occured, possibly due to not setting a checkpoint
during backup or something!?!?!
...anyway I am desperately tying to reduce the size of this file, and have
tried running the following:
USE Comms
GO
DBCC SHRINKFILE (Comms_log, 10)
and it just comes back and tells me:
- CurrentSize 608616
- Minimum Size 63
- UsedPages 608616
- EstimatedPages 56
with no reduction in LogFile size.
I also tried backing up just the databse and then restoring it under a
different name (so I can completely delete the old one and it's log!), but
when I try to restore it the system just comes back and tells me it hasn't
got enough space, even though it has just over 2GB (presumably it is trying,
or thinks it is trying to restore the log file as well, but goodness knows
where it's getting it from?!).
Any ideas?
Cheers, desperate Mike.
Mike,
What is the database recovery model? Is the log space unrestricted? Do you
take log backups?
If this is a Full recovery model DB then take a log backup. If the log in
unrestricted filegrowth give it a maximum size, just bigger than it is now.
Then you need to follow this: - http://support.microsoft.com/kb/873235/en-us
Chris
"Mike Owen" <whatnospam@.nospam.nospam> wrote in message
news:8CFFFB57-6B03-4DA3-95E7-BFD6B27C95A3@.microsoft.com...
> Hi,
> I have just come across a bit of a problem of my Windows 200 server
> running
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a
> checkpoint
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is
> trying,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>
|||Hi Mike,
Just do a transaction log backup and then try the shrink operation again.
If that does not work check if you have transactions or jobs running for a
long time.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:

> Hi,
> I have just come across a bit of a problem of my Windows 200 server running
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a checkpoint
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is trying,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>
|||Thanks for you reply Ben, and you Chris. I don't think I can take a log file
backup because I can oly do it on the local server and I haven't the space,
i.e. 2GB space and 4GB+ log file.
I have got a netwrok drive to a different server with space, but the SQL
server backp program doesn't see netwrok drives.
Any other ideas or a way I can backup to the network drive?
Cheers, Mike.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Mike,
> Just do a transaction log backup and then try the shrink operation again.
> If that does not work check if you have transactions or jobs running for a
> long time.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
|||If you do not have enough disk space then use the TRUNCATE_ONLY option like
in
backup log my_db with truncate_only
We are supposing you are not running in the SIMPLE recovery model. Is this
correct?
If that works, you must do a database backup at the end because by using
TRUNCATE_ONLY you are breaking the log chain.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
[vbcol=seagreen]
> Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> backup because I can oly do it on the local server and I haven't the space,
> i.e. 2GB space and 4GB+ log file.
> I have got a netwrok drive to a different server with space, but the SQL
> server backp program doesn't see netwrok drives.
> Any other ideas or a way I can backup to the network drive?
>
> Cheers, Mike.
> "Ben Nevarez" wrote:
|||Excuse my ignorance - It knows no bounds!
How do I know if I am using the SIMPLE recovery model?
I am quite happy to use: backup log my_db with truncate_only
The database isn't used very much, and I only backed it up about 1 1/2 hours
ago, so as long as I can recover that should something go wrong that would be
fine....but perhaps that isn't possible with the backup I have?!!?
Cheers, Mike.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> If you do not have enough disk space then use the TRUNCATE_ONLY option like
> in
> backup log my_db with truncate_only
> We are supposing you are not running in the SIMPLE recovery model. Is this
> correct?
> If that works, you must do a database backup at the end because by using
> TRUNCATE_ONLY you are breaking the log chain.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
|||Looks like you are not using the SIMPLE recovery model but try this
select databasepropertyex('my_db', 'recovery')
And also try the backup log with truncate_only and then shrink the log files.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
[vbcol=seagreen]
> Excuse my ignorance - It knows no bounds!
> How do I know if I am using the SIMPLE recovery model?
> I am quite happy to use: backup log my_db with truncate_only
> The database isn't used very much, and I only backed it up about 1 1/2 hours
> ago, so as long as I can recover that should something go wrong that would be
> fine....but perhaps that isn't possible with the backup I have?!!?
>
> Cheers, Mike.
> "Ben Nevarez" wrote:
|||The answer to select databasepropertyex('my_db', 'recovery')
is FULL.
I tried the '...try the backup log with truncate_only and then shrink the
log files' as you suggested and it WORKED!
I am now back to 7GB of space, plenty of room for growth for all the DB's,
and have restricted the size of all log files on the server.
Thanks for all your help, you got me out of a scrape!
Have a good weekend, cheers, Mike.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Looks like you are not using the SIMPLE recovery model but try this
> select databasepropertyex('my_db', 'recovery')
> And also try the backup log with truncate_only and then shrink the log files.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
|||Be careful about restricting the size of the log files ... SQL Server may
need this disk space.
Instead I would recommend scheduling transaction log backups periodically,
minimum daily. This will allow SQL Server to reuse the disk space used by the
transaction log files.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
[vbcol=seagreen]
> The answer to select databasepropertyex('my_db', 'recovery')
> is FULL.
> I tried the '...try the backup log with truncate_only and then shrink the
> log files' as you suggested and it WORKED!
> I am now back to 7GB of space, plenty of room for growth for all the DB's,
> and have restricted the size of all log files on the server.
> Thanks for all your help, you got me out of a scrape!
> Have a good weekend, cheers, Mike.
>
> "Ben Nevarez" wrote:
|||You can also create an alert that will run the log backup if you fill it
over a certain percent. Providing that you do not have any very large
transactions this should keep you safe.
Chris
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:7BBF5A0F-45E0-4493-9A95-F50FF7D05D20@.microsoft.com...[vbcol=seagreen]
> Be careful about restricting the size of the log files ... SQL Server may
> need this disk space.
> Instead I would recommend scheduling transaction log backups periodically,
> minimum daily. This will allow SQL Server to reuse the disk space used by
> the
> transaction log files.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:

Live server running out of space - Can't reduce Transaction Log!

Hi,
I have just come across a bit of a problem of my Windows 200 server running
SQL Server 2000....I am running out of space!
I have aout 2GB left. I have know this for some time, and for technical
reasons just found out I can't add a new disk...but that's another story.
I have looked at what I can reduce to increase the space, and it seems one
of the smaller database I have on the server, i.e. 16MB, has a log file of
4.8GB!
I am not sure why this has occured, possibly due to not setting a checkpoint
during backup or something!?!?!
...anyway I am desperately tying to reduce the size of this file, and have
tried running the following:
USE Comms
GO
DBCC SHRINKFILE (Comms_log, 10)
and it just comes back and tells me:
- CurrentSize 608616
- Minimum Size 63
- UsedPages 608616
- EstimatedPages 56
with no reduction in LogFile size.
I also tried backing up just the databse and then restoring it under a
different name (so I can completely delete the old one and it's log!), but
when I try to restore it the system just comes back and tells me it hasn't
got enough space, even though it has just over 2GB (presumably it is trying,
or thinks it is trying to restore the log file as well, but goodness knows
where it's getting it from?!).
Any ideas?
Cheers, desperate Mike.Mike,
What is the database recovery model? Is the log space unrestricted? Do you
take log backups?
If this is a Full recovery model DB then take a log backup. If the log in
unrestricted filegrowth give it a maximum size, just bigger than it is now.
Then you need to follow this: - http://support.microsoft.com/kb/873235/en-us
Chris
"Mike Owen" <whatnospam@.nospam.nospam> wrote in message
news:8CFFFB57-6B03-4DA3-95E7-BFD6B27C95A3@.microsoft.com...
> Hi,
> I have just come across a bit of a problem of my Windows 200 server
> running
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a
> checkpoint
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is
> trying,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>|||Hi Mike,
Just do a transaction log backup and then try the shrink operation again.
If that does not work check if you have transactions or jobs running for a
long time.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
> Hi,
> I have just come across a bit of a problem of my Windows 200 server running
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a checkpoint
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is trying,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>|||Thanks for you reply Ben, and you Chris. I don't think I can take a log file
backup because I can oly do it on the local server and I haven't the space,
i.e. 2GB space and 4GB+ log file.
I have got a netwrok drive to a different server with space, but the SQL
server backp program doesn't see netwrok drives.
Any other ideas or a way I can backup to the network drive?
Cheers, Mike.
"Ben Nevarez" wrote:
> Hi Mike,
> Just do a transaction log backup and then try the shrink operation again.
> If that does not work check if you have transactions or jobs running for a
> long time.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
> > Hi,
> >
> > I have just come across a bit of a problem of my Windows 200 server running
> > SQL Server 2000....I am running out of space!
> >
> > I have aout 2GB left. I have know this for some time, and for technical
> > reasons just found out I can't add a new disk...but that's another story.
> >
> > I have looked at what I can reduce to increase the space, and it seems one
> > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > 4.8GB!
> >
> > I am not sure why this has occured, possibly due to not setting a checkpoint
> > during backup or something!?!?!
> >
> > ...anyway I am desperately tying to reduce the size of this file, and have
> > tried running the following:
> >
> > USE Comms
> > GO
> > DBCC SHRINKFILE (Comms_log, 10)
> >
> > and it just comes back and tells me:
> > - CurrentSize 608616
> > - Minimum Size 63
> > - UsedPages 608616
> > - EstimatedPages 56
> >
> > with no reduction in LogFile size.
> >
> > I also tried backing up just the databse and then restoring it under a
> > different name (so I can completely delete the old one and it's log!), but
> > when I try to restore it the system just comes back and tells me it hasn't
> > got enough space, even though it has just over 2GB (presumably it is trying,
> > or thinks it is trying to restore the log file as well, but goodness knows
> > where it's getting it from?!).
> >
> > Any ideas?
> >
> > Cheers, desperate Mike.
> >|||If you do not have enough disk space then use the TRUNCATE_ONLY option like
in
backup log my_db with truncate_only
We are supposing you are not running in the SIMPLE recovery model. Is this
correct?
If that works, you must do a database backup at the end because by using
TRUNCATE_ONLY you are breaking the log chain.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
> Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> backup because I can oly do it on the local server and I haven't the space,
> i.e. 2GB space and 4GB+ log file.
> I have got a netwrok drive to a different server with space, but the SQL
> server backp program doesn't see netwrok drives.
> Any other ideas or a way I can backup to the network drive?
>
> Cheers, Mike.
> "Ben Nevarez" wrote:
> >
> > Hi Mike,
> >
> > Just do a transaction log backup and then try the shrink operation again.
> >
> > If that does not work check if you have transactions or jobs running for a
> > long time.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "Mike Owen" wrote:
> >
> > > Hi,
> > >
> > > I have just come across a bit of a problem of my Windows 200 server running
> > > SQL Server 2000....I am running out of space!
> > >
> > > I have aout 2GB left. I have know this for some time, and for technical
> > > reasons just found out I can't add a new disk...but that's another story.
> > >
> > > I have looked at what I can reduce to increase the space, and it seems one
> > > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > > 4.8GB!
> > >
> > > I am not sure why this has occured, possibly due to not setting a checkpoint
> > > during backup or something!?!?!
> > >
> > > ...anyway I am desperately tying to reduce the size of this file, and have
> > > tried running the following:
> > >
> > > USE Comms
> > > GO
> > > DBCC SHRINKFILE (Comms_log, 10)
> > >
> > > and it just comes back and tells me:
> > > - CurrentSize 608616
> > > - Minimum Size 63
> > > - UsedPages 608616
> > > - EstimatedPages 56
> > >
> > > with no reduction in LogFile size.
> > >
> > > I also tried backing up just the databse and then restoring it under a
> > > different name (so I can completely delete the old one and it's log!), but
> > > when I try to restore it the system just comes back and tells me it hasn't
> > > got enough space, even though it has just over 2GB (presumably it is trying,
> > > or thinks it is trying to restore the log file as well, but goodness knows
> > > where it's getting it from?!).
> > >
> > > Any ideas?
> > >
> > > Cheers, desperate Mike.
> > >|||Excuse my ignorance - It knows no bounds!
How do I know if I am using the SIMPLE recovery model?
I am quite happy to use: backup log my_db with truncate_only
The database isn't used very much, and I only backed it up about 1 1/2 hours
ago, so as long as I can recover that should something go wrong that would be
fine....but perhaps that isn't possible with the backup I have?!!?
Cheers, Mike.
"Ben Nevarez" wrote:
> If you do not have enough disk space then use the TRUNCATE_ONLY option like
> in
> backup log my_db with truncate_only
> We are supposing you are not running in the SIMPLE recovery model. Is this
> correct?
> If that works, you must do a database backup at the end because by using
> TRUNCATE_ONLY you are breaking the log chain.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
> > Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> > backup because I can oly do it on the local server and I haven't the space,
> > i.e. 2GB space and 4GB+ log file.
> >
> > I have got a netwrok drive to a different server with space, but the SQL
> > server backp program doesn't see netwrok drives.
> >
> > Any other ideas or a way I can backup to the network drive?
> >
> >
> > Cheers, Mike.
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Hi Mike,
> > >
> > > Just do a transaction log backup and then try the shrink operation again.
> > >
> > > If that does not work check if you have transactions or jobs running for a
> > > long time.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > > Senior Database Administrator
> > > AIG SunAmerica
> > >
> > >
> > >
> > > "Mike Owen" wrote:
> > >
> > > > Hi,
> > > >
> > > > I have just come across a bit of a problem of my Windows 200 server running
> > > > SQL Server 2000....I am running out of space!
> > > >
> > > > I have aout 2GB left. I have know this for some time, and for technical
> > > > reasons just found out I can't add a new disk...but that's another story.
> > > >
> > > > I have looked at what I can reduce to increase the space, and it seems one
> > > > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > > > 4.8GB!
> > > >
> > > > I am not sure why this has occured, possibly due to not setting a checkpoint
> > > > during backup or something!?!?!
> > > >
> > > > ...anyway I am desperately tying to reduce the size of this file, and have
> > > > tried running the following:
> > > >
> > > > USE Comms
> > > > GO
> > > > DBCC SHRINKFILE (Comms_log, 10)
> > > >
> > > > and it just comes back and tells me:
> > > > - CurrentSize 608616
> > > > - Minimum Size 63
> > > > - UsedPages 608616
> > > > - EstimatedPages 56
> > > >
> > > > with no reduction in LogFile size.
> > > >
> > > > I also tried backing up just the databse and then restoring it under a
> > > > different name (so I can completely delete the old one and it's log!), but
> > > > when I try to restore it the system just comes back and tells me it hasn't
> > > > got enough space, even though it has just over 2GB (presumably it is trying,
> > > > or thinks it is trying to restore the log file as well, but goodness knows
> > > > where it's getting it from?!).
> > > >
> > > > Any ideas?
> > > >
> > > > Cheers, desperate Mike.
> > > >|||Looks like you are not using the SIMPLE recovery model but try this
select databasepropertyex('my_db', 'recovery')
And also try the backup log with truncate_only and then shrink the log files.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
> Excuse my ignorance - It knows no bounds!
> How do I know if I am using the SIMPLE recovery model?
> I am quite happy to use: backup log my_db with truncate_only
> The database isn't used very much, and I only backed it up about 1 1/2 hours
> ago, so as long as I can recover that should something go wrong that would be
> fine....but perhaps that isn't possible with the backup I have?!!?
>
> Cheers, Mike.
> "Ben Nevarez" wrote:
> >
> > If you do not have enough disk space then use the TRUNCATE_ONLY option like
> > in
> >
> > backup log my_db with truncate_only
> >
> > We are supposing you are not running in the SIMPLE recovery model. Is this
> > correct?
> >
> > If that works, you must do a database backup at the end because by using
> > TRUNCATE_ONLY you are breaking the log chain.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "Mike Owen" wrote:
> >
> > > Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> > > backup because I can oly do it on the local server and I haven't the space,
> > > i.e. 2GB space and 4GB+ log file.
> > >
> > > I have got a netwrok drive to a different server with space, but the SQL
> > > server backp program doesn't see netwrok drives.
> > >
> > > Any other ideas or a way I can backup to the network drive?
> > >
> > >
> > > Cheers, Mike.
> > >
> > > "Ben Nevarez" wrote:
> > >
> > > >
> > > > Hi Mike,
> > > >
> > > > Just do a transaction log backup and then try the shrink operation again.
> > > >
> > > > If that does not work check if you have transactions or jobs running for a
> > > > long time.
> > > >
> > > > Hope this helps,
> > > >
> > > > Ben Nevarez
> > > > Senior Database Administrator
> > > > AIG SunAmerica
> > > >
> > > >
> > > >
> > > > "Mike Owen" wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have just come across a bit of a problem of my Windows 200 server running
> > > > > SQL Server 2000....I am running out of space!
> > > > >
> > > > > I have aout 2GB left. I have know this for some time, and for technical
> > > > > reasons just found out I can't add a new disk...but that's another story.
> > > > >
> > > > > I have looked at what I can reduce to increase the space, and it seems one
> > > > > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > > > > 4.8GB!
> > > > >
> > > > > I am not sure why this has occured, possibly due to not setting a checkpoint
> > > > > during backup or something!?!?!
> > > > >
> > > > > ...anyway I am desperately tying to reduce the size of this file, and have
> > > > > tried running the following:
> > > > >
> > > > > USE Comms
> > > > > GO
> > > > > DBCC SHRINKFILE (Comms_log, 10)
> > > > >
> > > > > and it just comes back and tells me:
> > > > > - CurrentSize 608616
> > > > > - Minimum Size 63
> > > > > - UsedPages 608616
> > > > > - EstimatedPages 56
> > > > >
> > > > > with no reduction in LogFile size.
> > > > >
> > > > > I also tried backing up just the databse and then restoring it under a
> > > > > different name (so I can completely delete the old one and it's log!), but
> > > > > when I try to restore it the system just comes back and tells me it hasn't
> > > > > got enough space, even though it has just over 2GB (presumably it is trying,
> > > > > or thinks it is trying to restore the log file as well, but goodness knows
> > > > > where it's getting it from?!).
> > > > >
> > > > > Any ideas?
> > > > >
> > > > > Cheers, desperate Mike.
> > > > >|||The answer to select databasepropertyex('my_db', 'recovery')
is FULL.
I tried the '...try the backup log with truncate_only and then shrink the
log files' as you suggested and it WORKED!
I am now back to 7GB of space, plenty of room for growth for all the DB's,
and have restricted the size of all log files on the server.
Thanks for all your help, you got me out of a scrape!
Have a good weekend, cheers, Mike.
"Ben Nevarez" wrote:
> Looks like you are not using the SIMPLE recovery model but try this
> select databasepropertyex('my_db', 'recovery')
> And also try the backup log with truncate_only and then shrink the log files.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
> > Excuse my ignorance - It knows no bounds!
> >
> > How do I know if I am using the SIMPLE recovery model?
> >
> > I am quite happy to use: backup log my_db with truncate_only
> >
> > The database isn't used very much, and I only backed it up about 1 1/2 hours
> > ago, so as long as I can recover that should something go wrong that would be
> > fine....but perhaps that isn't possible with the backup I have?!!?
> >
> >
> > Cheers, Mike.
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > If you do not have enough disk space then use the TRUNCATE_ONLY option like
> > > in
> > >
> > > backup log my_db with truncate_only
> > >
> > > We are supposing you are not running in the SIMPLE recovery model. Is this
> > > correct?
> > >
> > > If that works, you must do a database backup at the end because by using
> > > TRUNCATE_ONLY you are breaking the log chain.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > > Senior Database Administrator
> > > AIG SunAmerica
> > >
> > >
> > >
> > > "Mike Owen" wrote:
> > >
> > > > Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> > > > backup because I can oly do it on the local server and I haven't the space,
> > > > i.e. 2GB space and 4GB+ log file.
> > > >
> > > > I have got a netwrok drive to a different server with space, but the SQL
> > > > server backp program doesn't see netwrok drives.
> > > >
> > > > Any other ideas or a way I can backup to the network drive?
> > > >
> > > >
> > > > Cheers, Mike.
> > > >
> > > > "Ben Nevarez" wrote:
> > > >
> > > > >
> > > > > Hi Mike,
> > > > >
> > > > > Just do a transaction log backup and then try the shrink operation again.
> > > > >
> > > > > If that does not work check if you have transactions or jobs running for a
> > > > > long time.
> > > > >
> > > > > Hope this helps,
> > > > >
> > > > > Ben Nevarez
> > > > > Senior Database Administrator
> > > > > AIG SunAmerica
> > > > >
> > > > >
> > > > >
> > > > > "Mike Owen" wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I have just come across a bit of a problem of my Windows 200 server running
> > > > > > SQL Server 2000....I am running out of space!
> > > > > >
> > > > > > I have aout 2GB left. I have know this for some time, and for technical
> > > > > > reasons just found out I can't add a new disk...but that's another story.
> > > > > >
> > > > > > I have looked at what I can reduce to increase the space, and it seems one
> > > > > > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > > > > > 4.8GB!
> > > > > >
> > > > > > I am not sure why this has occured, possibly due to not setting a checkpoint
> > > > > > during backup or something!?!?!
> > > > > >
> > > > > > ...anyway I am desperately tying to reduce the size of this file, and have
> > > > > > tried running the following:
> > > > > >
> > > > > > USE Comms
> > > > > > GO
> > > > > > DBCC SHRINKFILE (Comms_log, 10)
> > > > > >
> > > > > > and it just comes back and tells me:
> > > > > > - CurrentSize 608616
> > > > > > - Minimum Size 63
> > > > > > - UsedPages 608616
> > > > > > - EstimatedPages 56
> > > > > >
> > > > > > with no reduction in LogFile size.
> > > > > >
> > > > > > I also tried backing up just the databse and then restoring it under a
> > > > > > different name (so I can completely delete the old one and it's log!), but
> > > > > > when I try to restore it the system just comes back and tells me it hasn't
> > > > > > got enough space, even though it has just over 2GB (presumably it is trying,
> > > > > > or thinks it is trying to restore the log file as well, but goodness knows
> > > > > > where it's getting it from?!).
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > Cheers, desperate Mike.
> > > > > >|||Be careful about restricting the size of the log files ... SQL Server may
need this disk space.
Instead I would recommend scheduling transaction log backups periodically,
minimum daily. This will allow SQL Server to reuse the disk space used by the
transaction log files.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:
> The answer to select databasepropertyex('my_db', 'recovery')
> is FULL.
> I tried the '...try the backup log with truncate_only and then shrink the
> log files' as you suggested and it WORKED!
> I am now back to 7GB of space, plenty of room for growth for all the DB's,
> and have restricted the size of all log files on the server.
> Thanks for all your help, you got me out of a scrape!
> Have a good weekend, cheers, Mike.
>
> "Ben Nevarez" wrote:
> >
> > Looks like you are not using the SIMPLE recovery model but try this
> >
> > select databasepropertyex('my_db', 'recovery')
> >
> > And also try the backup log with truncate_only and then shrink the log files.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "Mike Owen" wrote:
> >
> > > Excuse my ignorance - It knows no bounds!
> > >
> > > How do I know if I am using the SIMPLE recovery model?
> > >
> > > I am quite happy to use: backup log my_db with truncate_only
> > >
> > > The database isn't used very much, and I only backed it up about 1 1/2 hours
> > > ago, so as long as I can recover that should something go wrong that would be
> > > fine....but perhaps that isn't possible with the backup I have?!!?
> > >
> > >
> > > Cheers, Mike.
> > >
> > > "Ben Nevarez" wrote:
> > >
> > > >
> > > > If you do not have enough disk space then use the TRUNCATE_ONLY option like
> > > > in
> > > >
> > > > backup log my_db with truncate_only
> > > >
> > > > We are supposing you are not running in the SIMPLE recovery model. Is this
> > > > correct?
> > > >
> > > > If that works, you must do a database backup at the end because by using
> > > > TRUNCATE_ONLY you are breaking the log chain.
> > > >
> > > > Hope this helps,
> > > >
> > > > Ben Nevarez
> > > > Senior Database Administrator
> > > > AIG SunAmerica
> > > >
> > > >
> > > >
> > > > "Mike Owen" wrote:
> > > >
> > > > > Thanks for you reply Ben, and you Chris. I don't think I can take a log file
> > > > > backup because I can oly do it on the local server and I haven't the space,
> > > > > i.e. 2GB space and 4GB+ log file.
> > > > >
> > > > > I have got a netwrok drive to a different server with space, but the SQL
> > > > > server backp program doesn't see netwrok drives.
> > > > >
> > > > > Any other ideas or a way I can backup to the network drive?
> > > > >
> > > > >
> > > > > Cheers, Mike.
> > > > >
> > > > > "Ben Nevarez" wrote:
> > > > >
> > > > > >
> > > > > > Hi Mike,
> > > > > >
> > > > > > Just do a transaction log backup and then try the shrink operation again.
> > > > > >
> > > > > > If that does not work check if you have transactions or jobs running for a
> > > > > > long time.
> > > > > >
> > > > > > Hope this helps,
> > > > > >
> > > > > > Ben Nevarez
> > > > > > Senior Database Administrator
> > > > > > AIG SunAmerica
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Mike Owen" wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have just come across a bit of a problem of my Windows 200 server running
> > > > > > > SQL Server 2000....I am running out of space!
> > > > > > >
> > > > > > > I have aout 2GB left. I have know this for some time, and for technical
> > > > > > > reasons just found out I can't add a new disk...but that's another story.
> > > > > > >
> > > > > > > I have looked at what I can reduce to increase the space, and it seems one
> > > > > > > of the smaller database I have on the server, i.e. 16MB, has a log file of
> > > > > > > 4.8GB!
> > > > > > >
> > > > > > > I am not sure why this has occured, possibly due to not setting a checkpoint
> > > > > > > during backup or something!?!?!
> > > > > > >
> > > > > > > ...anyway I am desperately tying to reduce the size of this file, and have
> > > > > > > tried running the following:
> > > > > > >
> > > > > > > USE Comms
> > > > > > > GO
> > > > > > > DBCC SHRINKFILE (Comms_log, 10)
> > > > > > >
> > > > > > > and it just comes back and tells me:
> > > > > > > - CurrentSize 608616
> > > > > > > - Minimum Size 63
> > > > > > > - UsedPages 608616
> > > > > > > - EstimatedPages 56
> > > > > > >
> > > > > > > with no reduction in LogFile size.
> > > > > > >
> > > > > > > I also tried backing up just the databse and then restoring it under a
> > > > > > > different name (so I can completely delete the old one and it's log!), but
> > > > > > > when I try to restore it the system just comes back and tells me it hasn't
> > > > > > > got enough space, even though it has just over 2GB (presumably it is trying,
> > > > > > > or thinks it is trying to restore the log file as well, but goodness knows
> > > > > > > where it's getting it from?!).
> > > > > > >
> > > > > > > Any ideas?
> > > > > > >
> > > > > > > Cheers, desperate Mike.
> > > > > > >|||You can also create an alert that will run the log backup if you fill it
over a certain percent. Providing that you do not have any very large
transactions this should keep you safe.
Chris
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:7BBF5A0F-45E0-4493-9A95-F50FF7D05D20@.microsoft.com...
> Be careful about restricting the size of the log files ... SQL Server may
> need this disk space.
> Instead I would recommend scheduling transaction log backups periodically,
> minimum daily. This will allow SQL Server to reuse the disk space used by
> the
> transaction log files.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Mike Owen" wrote:
>> The answer to select databasepropertyex('my_db', 'recovery')
>> is FULL.
>> I tried the '...try the backup log with truncate_only and then shrink
>> the
>> log files' as you suggested and it WORKED!
>> I am now back to 7GB of space, plenty of room for growth for all the
>> DB's,
>> and have restricted the size of all log files on the server.
>> Thanks for all your help, you got me out of a scrape!
>> Have a good weekend, cheers, Mike.
>>
>> "Ben Nevarez" wrote:
>> >
>> > Looks like you are not using the SIMPLE recovery model but try this
>> >
>> > select databasepropertyex('my_db', 'recovery')
>> >
>> > And also try the backup log with truncate_only and then shrink the log
>> > files.
>> >
>> > Hope this helps,
>> >
>> > Ben Nevarez
>> > Senior Database Administrator
>> > AIG SunAmerica
>> >
>> >
>> >
>> > "Mike Owen" wrote:
>> >
>> > > Excuse my ignorance - It knows no bounds!
>> > >
>> > > How do I know if I am using the SIMPLE recovery model?
>> > >
>> > > I am quite happy to use: backup log my_db with truncate_only
>> > >
>> > > The database isn't used very much, and I only backed it up about 1
>> > > 1/2 hours
>> > > ago, so as long as I can recover that should something go wrong that
>> > > would be
>> > > fine....but perhaps that isn't possible with the backup I have?!!?
>> > >
>> > >
>> > > Cheers, Mike.
>> > >
>> > > "Ben Nevarez" wrote:
>> > >
>> > > >
>> > > > If you do not have enough disk space then use the TRUNCATE_ONLY
>> > > > option like
>> > > > in
>> > > >
>> > > > backup log my_db with truncate_only
>> > > >
>> > > > We are supposing you are not running in the SIMPLE recovery model.
>> > > > Is this
>> > > > correct?
>> > > >
>> > > > If that works, you must do a database backup at the end because by
>> > > > using
>> > > > TRUNCATE_ONLY you are breaking the log chain.
>> > > >
>> > > > Hope this helps,
>> > > >
>> > > > Ben Nevarez
>> > > > Senior Database Administrator
>> > > > AIG SunAmerica
>> > > >
>> > > >
>> > > >
>> > > > "Mike Owen" wrote:
>> > > >
>> > > > > Thanks for you reply Ben, and you Chris. I don't think I can
>> > > > > take a log file
>> > > > > backup because I can oly do it on the local server and I haven't
>> > > > > the space,
>> > > > > i.e. 2GB space and 4GB+ log file.
>> > > > >
>> > > > > I have got a netwrok drive to a different server with space, but
>> > > > > the SQL
>> > > > > server backp program doesn't see netwrok drives.
>> > > > >
>> > > > > Any other ideas or a way I can backup to the network drive?
>> > > > >
>> > > > >
>> > > > > Cheers, Mike.
>> > > > >
>> > > > > "Ben Nevarez" wrote:
>> > > > >
>> > > > > >
>> > > > > > Hi Mike,
>> > > > > >
>> > > > > > Just do a transaction log backup and then try the shrink
>> > > > > > operation again.
>> > > > > >
>> > > > > > If that does not work check if you have transactions or jobs
>> > > > > > running for a
>> > > > > > long time.
>> > > > > >
>> > > > > > Hope this helps,
>> > > > > >
>> > > > > > Ben Nevarez
>> > > > > > Senior Database Administrator
>> > > > > > AIG SunAmerica
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > "Mike Owen" wrote:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > I have just come across a bit of a problem of my Windows 200
>> > > > > > > server running
>> > > > > > > SQL Server 2000....I am running out of space!
>> > > > > > >
>> > > > > > > I have aout 2GB left. I have know this for some time, and
>> > > > > > > for technical
>> > > > > > > reasons just found out I can't add a new disk...but that's
>> > > > > > > another story.
>> > > > > > >
>> > > > > > > I have looked at what I can reduce to increase the space, and
>> > > > > > > it seems one
>> > > > > > > of the smaller database I have on the server, i.e. 16MB, has
>> > > > > > > a log file of
>> > > > > > > 4.8GB!
>> > > > > > >
>> > > > > > > I am not sure why this has occured, possibly due to not
>> > > > > > > setting a checkpoint
>> > > > > > > during backup or something!?!?!
>> > > > > > >
>> > > > > > > ...anyway I am desperately tying to reduce the size of this
>> > > > > > > file, and have
>> > > > > > > tried running the following:
>> > > > > > >
>> > > > > > > USE Comms
>> > > > > > > GO
>> > > > > > > DBCC SHRINKFILE (Comms_log, 10)
>> > > > > > >
>> > > > > > > and it just comes back and tells me:
>> > > > > > > - CurrentSize 608616
>> > > > > > > - Minimum Size 63
>> > > > > > > - UsedPages 608616
>> > > > > > > - EstimatedPages 56
>> > > > > > >
>> > > > > > > with no reduction in LogFile size.
>> > > > > > >
>> > > > > > > I also tried backing up just the databse and then restoring
>> > > > > > > it under a
>> > > > > > > different name (so I can completely delete the old one and
>> > > > > > > it's log!), but
>> > > > > > > when I try to restore it the system just comes back and tells
>> > > > > > > me it hasn't
>> > > > > > > got enough space, even though it has just over 2GB
>> > > > > > > (presumably it is trying,
>> > > > > > > or thinks it is trying to restore the log file as well, but
>> > > > > > > goodness knows
>> > > > > > > where it's getting it from?!).
>> > > > > > >
>> > > > > > > Any ideas?
>> > > > > > >
>> > > > > > > Cheers, desperate Mike.
>> > > > > > >

Live server running out of space - Can't reduce Transaction Log!

Hi,
I have just come across a bit of a problem of my Windows 200 server running
SQL Server 2000....I am running out of space!
I have aout 2GB left. I have know this for some time, and for technical
reasons just found out I can't add a new disk...but that's another story.
I have looked at what I can reduce to increase the space, and it seems one
of the smaller database I have on the server, i.e. 16MB, has a log file of
4.8GB!
I am not sure why this has occured, possibly due to not setting a checkpoint
during backup or something!?!?!
...anyway I am desperately tying to reduce the size of this file, and have
tried running the following:
USE Comms
GO
DBCC SHRINKFILE (Comms_log, 10)
and it just comes back and tells me:
- CurrentSize 608616
- Minimum Size 63
- UsedPages 608616
- EstimatedPages 56
with no reduction in LogFile size.
I also tried backing up just the databse and then restoring it under a
different name (so I can completely delete the old one and it's log!), but
when I try to restore it the system just comes back and tells me it hasn't
got enough space, even though it has just over 2GB (presumably it is trying,
or thinks it is trying to restore the log file as well, but goodness knows
where it's getting it from?!).
Any ideas?
Cheers, desperate Mike.Mike,
What is the database recovery model? Is the log space unrestricted? Do you
take log backups?
If this is a Full recovery model DB then take a log backup. If the log in
unrestricted filegrowth give it a maximum size, just bigger than it is now.
Then you need to follow this: - http://support.microsoft.com/kb/873235/en-us
Chris
"Mike Owen" <whatnospam@.nospam.nospam> wrote in message
news:8CFFFB57-6B03-4DA3-95E7-BFD6B27C95A3@.microsoft.com...
> Hi,
> I have just come across a bit of a problem of my Windows 200 server
> running
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a
> checkpoint
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is
> trying,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>|||Hi Mike,
Just do a transaction log backup and then try the shrink operation again.
If that does not work check if you have transactions or jobs running for a
long time.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Mike Owen" wrote:

> Hi,
> I have just come across a bit of a problem of my Windows 200 server runnin
g
> SQL Server 2000....I am running out of space!
> I have aout 2GB left. I have know this for some time, and for technical
> reasons just found out I can't add a new disk...but that's another story.
> I have looked at what I can reduce to increase the space, and it seems one
> of the smaller database I have on the server, i.e. 16MB, has a log file of
> 4.8GB!
> I am not sure why this has occured, possibly due to not setting a checkpoi
nt
> during backup or something!?!?!
> ...anyway I am desperately tying to reduce the size of this file, and have
> tried running the following:
> USE Comms
> GO
> DBCC SHRINKFILE (Comms_log, 10)
> and it just comes back and tells me:
> - CurrentSize 608616
> - Minimum Size 63
> - UsedPages 608616
> - EstimatedPages 56
> with no reduction in LogFile size.
> I also tried backing up just the databse and then restoring it under a
> different name (so I can completely delete the old one and it's log!), but
> when I try to restore it the system just comes back and tells me it hasn't
> got enough space, even though it has just over 2GB (presumably it is tryin
g,
> or thinks it is trying to restore the log file as well, but goodness knows
> where it's getting it from?!).
> Any ideas?
> Cheers, desperate Mike.
>

Live Onecare subscription lost

Hi

I got the following error message when I make a new integration service project

Failed to save package file "C:\Documents and Settings\Administrator\Local Settings\Temp\1\tmp2B.tmp" with error 0x80040155 "Interface not registered".
Can someone help

MeHi there,

This looks like a setup issue. Did you have a prior build of SQL/VS 2005 on the machine? If so, likely the machine wasn't cleaned up prior to setting up.

regards,
ash|||I also am getting this error.
I upgraded from VS 2005 Beta 2 to VS 2005 RC, but I followed all recommended uninstallation steps prior to installing VS 2005 RC.
So what can I do about this?
Will it help at all to completely uninstall VS 2005 RC and then reinstall it?
I've already tried repairing VS 2005 RC, but it didn't make any difference.
Thanks,
Dyvim|||Try registering MSXML:

regsvr32 msxml3.dll
regsvr32 msxml6.dll|||Thanks, this worked also for me|||Thanks but how do I do this, how do I register MSXML?|||

Just run these two commands from the command prompt:

regsvr32 msxml3.dll
regsvr32 msxml6.dll

|||yes it works for me too. Thanks.|||

I got the same issue, it also works for me.

Thank you so much!

|||

Hi-Thank you for the info. When I ran the 1st command regsvr32 msxml3.dll, it went fine. The 2nd command regsvr32 msxml6.dll told me "The specific module could not be found" I am getting errors like: Interface not registered (when I try to print), No such interface supported (when I tried to contact NoAdware for online support). Also, get same message when I try to go into a game room on Yahoo games. Please note: I just did a scan to remove adware and spyware.

Thanks in advance for any help you can give me,

Corinne

|||

It looks like the software you used to "remove adware and spyware" removed much more - apparently it deleted msxml6.dll (which is installed with SQL Server 2005) and probably some interface registrations.

I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.

|||

Hi, I have the exact same problem but it is when I try to burn a cd using Win Media Player 10. I tried registering the .dll's, but since I don't have the SQL 2005 installed in my machine, the regsvr32 msxml6.dll gives me the same error message. I see that this forum is mainly for SQL but if anybody knows what I can do, it would be appreciated.

Thanks,

Jason

|||

Hi there, di you get a reply to your query as I am experiencing the same problem. Please e-mail me & let me know. Many thanks

|||

Guys, there are thousands of interfaces registered on a typical Windows box. The error can be caused by missing registration of any of them.

We've found that particular problem ("Interface not registered" error when creating new SSIS project) is usually caused by incorrectly registered msxml dlls - my reply above describes how to fix it.

Regarding other applications - like media player, etc - there is no common answer, and you should be looking at the support forums for particular application.

|||

Quote 'I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.'

If I had to re-format every time something is not registering in Windows - that would be all I would be doing -Re-formatting...

Would re-installing SQL fix the problem.

Dan.

sql

Live communication Address book service

Hi, when I try to activate my address book, i get the error "There is no pool available for this operation. Exit the wizard. (Error Code: 0xc3EC78D9)".

I have verified my mmc shows that LCS is at SP1, it is activated, and
functioning properly (users able to interact via OC2005). It is locally
installed on the standard edition server.

As per the Technet reference :

Possible causes include:

?

The Live Communications Server service is not running on the pool or server.

?

No servers or pools in your topology have been upgraded to Service Pack 1.

?

The Standard Edition Server is not activated, or none of the Enterprise Edition Servers within a pool are activated. Check your servers.

?

You want to run the Address Book Service on a Standard Edition Server, but you have installed the Address Book Service on a separate computer. The Address Book Service must be installed locally on a Standard Edition Server to work in this deployment.

Live communication Address book service

Hi, when I try to activate my address book, i get the error "There is no pool available for this operation. Exit the wizard. (Error Code: 0xc3EC78D9)".

I have verified my mmc shows that LCS is at SP1, it is activated, and
functioning properly (users able to interact via OC2005). It is locally
installed on the standard edition server.

As per the Technet reference :

Possible causes include:

?

The Live Communications Server service is not running on the pool or server.

?

No servers or pools in your topology have been upgraded to Service Pack 1.

?

The Standard Edition Server is not activated, or none of the Enterprise Edition Servers within a pool are activated. Check your servers.

?

You want to run the Address Book Service on a Standard Edition Server, but you have installed the Address Book Service on a separate computer. The Address Book Service must be installed locally on a Standard Edition Server to work in this deployment.

|||

What about that same error in Office Communications Server 2007? I get that same error code when trying to set up my edge server.

Live backups

I consider the documentation on this topic somewhat confusing, so I figured
I'd ask here.
If I use any one of the common network backup utilities, and tell it to
"live backup" my database and log, will this work as a backup?
Right now I'm doing a full backup every night, but we DO have such software
installed that's backing up the rest of our systems live onto offsite
storage. I consider this to be much "safer", and if we can use this on our
SQL Server as well, I would rest better.
MauryMaury
You will find that most sites use the native SQL Server backup to back the
databases up to disk and then use something like Legato or Backup exec to
copy them from disk to offsite storage.
There are several reasons for doing it this way. Certainly most of the
backup programs did not work very well with SQL Server in older versions. It
was always a bit hit of miss if you could actually restore your backups. Most
of the main tools do know have SQL Server speciffic modules now, which means
they are better at backing up SQL Server.
Using the native SQL Server backup means no version problem issues, which
can be useful.
By using the SQL Server backup to disk you have an easily accessable version
of the backup. This can be useful if you need to restore from it or want to
copy it to another server for support purposes.
The bottom line is that most people use native SQL Server backup to disk and
then a third party tool, because in most cases it is the best way to do it.
Regards
John
"Maury Markowitz" wrote:
> I consider the documentation on this topic somewhat confusing, so I figured
> I'd ask here.
> If I use any one of the common network backup utilities, and tell it to
> "live backup" my database and log, will this work as a backup?
> Right now I'm doing a full backup every night, but we DO have such software
> installed that's backing up the rest of our systems live onto offsite
> storage. I consider this to be much "safer", and if we can use this on our
> SQL Server as well, I would rest better.
> Maury|||"John Bandettini" wrote:
> There are several reasons for doing it this way. Certainly most of the
> backup programs did not work very well with SQL Server in older versions.
Can you be more specific on this particular issue? We're currently running
SS2k, is this one of the "older versions" you mention? Do you know what sort
of problems should be expected in these cases?
Technically it seems there shouldn't be a problem. Writes to the logs should
be flushed through immediately, which is what I would suspect COULD cause a
problem.
Maury|||Maury Markowitz wrote:
> "John Bandettini" wrote:
> Technically it seems there shouldn't be a problem. Writes to the logs should
> be flushed through immediately, which is what I would suspect COULD cause a
> problem.
John's point, and the general consensus, is that it is FAR safer to
rely on the built-in native SQL Server backup utility to create the
database backups, than on a third-party tool. Use the SQL BACKUP
command to dump the database and/or t-logs to disk, then backup those
disk files using your favorite backup tool. Far more flexible, far
more reliable, you'll save yourself much grief doing it this way.|||"Tracy McKibben" wrote:
> John's point, and the general consensus, is that it is FAR safer to
> rely on the built-in native SQL Server backup utility to create the
> database backups, than on a third-party tool. Use the SQL BACKUP
But the problem with this approach is that it only gets done "every so
often". A failure is more likely to occur during the day (high activity) that
at night when the backups run, so the delay between a nightly backup and the
failure represents a real risk for loss of data.
Let's approach this another way: is there a product that bills itself as a
suitable real-time backup system for SS 2k?
Maury|||Maury Markowitz wrote:
> But the problem with this approach is that it only gets done "every so
> often". A failure is more likely to occur during the day (high activity) that
> at night when the backups run, so the delay between a nightly backup and the
> failure represents a real risk for loss of data.
> Let's approach this another way: is there a product that bills itself as a
> suitable real-time backup system for SS 2k?
What you're saying is true if you're only running FULL database
backups. You also have to ability to do transaction log backups, at
any interval you'd like. The transaction log is a record of every
change that occurs within the database. If you backup the transaction
log at regular intervals, let's say 15 minutes, you'll never lose more
than 15 minutes of data should a failure occur.
For instance, on my production servers, full database backups are done
nightly. After that, a transaction log backup is done every 5 minutes.
We also log-ship those backups to a standby database. Should a
database failure occur, we are virtually guaranteed not to lose more
than 5 minutes worth of data.|||Tracy McKibben wrote:
> What you're saying is true if you're only running FULL database
> backups. You also have to ability to do transaction log backups, at
> any interval you'd like. The transaction log is a record of every
> change that occurs within the database. If you backup the transaction
> log at regular intervals, let's say 15 minutes, you'll never lose more
> than 15 minutes of data should a failure occur.
> For instance, on my production servers, full database backups are done
> nightly. After that, a transaction log backup is done every 5 minutes.
> We also log-ship those backups to a standby database. Should a
> database failure occur, we are virtually guaranteed not to lose more
> than 5 minutes worth of data.
Also, your database must be in "Full" or "Bulk-Logged" recovery mode to
do transaction log backups.|||Maury Markowitz wrote:
> "Tracy McKibben" wrote:
>>John's point, and the general consensus, is that it is FAR safer to
>>rely on the built-in native SQL Server backup utility to create the
>>database backups, than on a third-party tool. Use the SQL BACKUP
>
> But the problem with this approach is that it only gets done "every so
> often". A failure is more likely to occur during the day (high activity) that
> at night when the backups run, so the delay between a nightly backup and the
> failure represents a real risk for loss of data.
> Let's approach this another way: is there a product that bills itself as a
> suitable real-time backup system for SS 2k?
> Maury
Hi Maury
No backup systems I'm aware of is more "real-time" than what you can do
with SQL servers native backup.
The procedure is to e.g. backup your database once every night, and then
run transaction log backups every so and so often (e.g. every 15
minutes). By doing it this way you will always (at least) be able to
restore your database to the state it was in 15 minutes before it got
damaged. Depending on what has gone wrong, you'll actually in many case
be able to take a backup of you actual logfile and then also apply this
log backup with the STOP AT option that will stop the restore at the
time just before things went wrong.
In my opinion this is the most reliable and safe backup method and I'm
not aware of anything that can do it better.
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:8E7F0399-3216-4225-B100-028971F92AE1@.microsoft.com...
> "Tracy McKibben" wrote:
> > John's point, and the general consensus, is that it is FAR safer to
> > rely on the built-in native SQL Server backup utility to create the
> > database backups, than on a third-party tool. Use the SQL BACKUP
> But the problem with this approach is that it only gets done "every so
> often".
Why?
You can schedule full backups and transaction log backups whenever you want.
We do full backups 3 times a week and transaction log backups every 20
minutes.
This means we're never more than 20 minutes out.
> A failure is more likely to occur during the day (high activity) that
> at night when the backups run, so the delay between a nightly backup and
the
> failure represents a real risk for loss of data.
> Let's approach this another way: is there a product that bills itself as a
> suitable real-time backup system for SS 2k?
Yes. SQL Server 2000 itself.
Unless you've got a VLDB or special needs, it can meet the needs of most
users out there.
You can also look at something like SQL Litespeed to speed things up though.
> Maury

Live backups

Maury
You will find that most sites use the native SQL Server backup to back the
databases up to disk and then use something like Legato or Backup exec to
copy them from disk to offsite storage.
There are several reasons for doing it this way. Certainly most of the
backup programs did not work very well with SQL Server in older versions. It
was always a bit hit of miss if you could actually restore your backups. Mos
t
of the main tools do know have SQL Server speciffic modules now, which means
they are better at backing up SQL Server.
Using the native SQL Server backup means no version problem issues, which
can be useful.
By using the SQL Server backup to disk you have an easily accessable version
of the backup. This can be useful if you need to restore from it or want to
copy it to another server for support purposes.
The bottom line is that most people use native SQL Server backup to disk and
then a third party tool, because in most cases it is the best way to do it.
Regards
John
"Maury Markowitz" wrote:

> I consider the documentation on this topic somewhat confusing, so I figure
d
> I'd ask here.
> If I use any one of the common network backup utilities, and tell it to
> "live backup" my database and log, will this work as a backup?
> Right now I'm doing a full backup every night, but we DO have such softwar
e
> installed that's backing up the rest of our systems live onto offsite
> storage. I consider this to be much "safer", and if we can use this on our
> SQL Server as well, I would rest better.
> Maury"John Bandettini" wrote:

> There are several reasons for doing it this way. Certainly most of the
> backup programs did not work very well with SQL Server in older versions.
Can you be more specific on this particular issue? We're currently running
SS2k, is this one of the "older versions" you mention? Do you know what sort
of problems should be expected in these cases?
Technically it seems there shouldn't be a problem. Writes to the logs should
be flushed through immediately, which is what I would suspect COULD cause a
problem.
Maury|||Maury Markowitz wrote:
> "John Bandettini" wrote:
> Technically it seems there shouldn't be a problem. Writes to the logs shou
ld
> be flushed through immediately, which is what I would suspect COULD cause
a
> problem.
John's point, and the general consensus, is that it is FAR safer to
rely on the built-in native SQL Server backup utility to create the
database backups, than on a third-party tool. Use the SQL BACKUP
command to dump the database and/or t-logs to disk, then backup those
disk files using your favorite backup tool. Far more flexible, far
more reliable, you'll save yourself much grief doing it this way.|||"Tracy McKibben" wrote:
> John's point, and the general consensus, is that it is FAR safer to
> rely on the built-in native SQL Server backup utility to create the
> database backups, than on a third-party tool. Use the SQL BACKUP
But the problem with this approach is that it only gets done "every so
often". A failure is more likely to occur during the day (high activity) tha
t
at night when the backups run, so the delay between a nightly backup and the
failure represents a real risk for loss of data.
Let's approach this another way: is there a product that bills itself as a
suitable real-time backup system for SS 2k?
Maury|||Maury Markowitz wrote:
> But the problem with this approach is that it only gets done "every so
> often". A failure is more likely to occur during the day (high activity) t
hat
> at night when the backups run, so the delay between a nightly backup and t
he
> failure represents a real risk for loss of data.
> Let's approach this another way: is there a product that bills itself as a
> suitable real-time backup system for SS 2k?
What you're saying is true if you're only running FULL database
backups. You also have to ability to do transaction log backups, at
any interval you'd like. The transaction log is a record of every
change that occurs within the database. If you backup the transaction
log at regular intervals, let's say 15 minutes, you'll never lose more
than 15 minutes of data should a failure occur.
For instance, on my production servers, full database backups are done
nightly. After that, a transaction log backup is done every 5 minutes.
We also log-ship those backups to a standby database. Should a
database failure occur, we are virtually guaranteed not to lose more
than 5 minutes worth of data.|||Tracy McKibben wrote:
> What you're saying is true if you're only running FULL database
> backups. You also have to ability to do transaction log backups, at
> any interval you'd like. The transaction log is a record of every
> change that occurs within the database. If you backup the transaction
> log at regular intervals, let's say 15 minutes, you'll never lose more
> than 15 minutes of data should a failure occur.
> For instance, on my production servers, full database backups are done
> nightly. After that, a transaction log backup is done every 5 minutes.
> We also log-ship those backups to a standby database. Should a
> database failure occur, we are virtually guaranteed not to lose more
> than 5 minutes worth of data.
Also, your database must be in "Full" or "Bulk-Logged" recovery mode to
do transaction log backups.|||Maury Markowitz wrote:
> "Tracy McKibben" wrote:
>
>
> But the problem with this approach is that it only gets done "every so
> often". A failure is more likely to occur during the day (high activity) t
hat
> at night when the backups run, so the delay between a nightly backup and t
he
> failure represents a real risk for loss of data.
> Let's approach this another way: is there a product that bills itself as a
> suitable real-time backup system for SS 2k?
> Maury
Hi Maury
No backup systems I'm aware of is more "real-time" than what you can do
with SQL servers native backup.
The procedure is to e.g. backup your database once every night, and then
run transaction log backups every so and so often (e.g. every 15
minutes). By doing it this way you will always (at least) be able to
restore your database to the state it was in 15 minutes before it got
damaged. Depending on what has gone wrong, you'll actually in many case
be able to take a backup of you actual logfile and then also apply this
log backup with the STOP AT option that will stop the restore at the
time just before things went wrong.
In my opinion this is the most reliable and safe backup method and I'm
not aware of anything that can do it better.
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||I consider the documentation on this topic somewhat confusing, so I figured
I'd ask here.
If I use any one of the common network backup utilities, and tell it to
"live backup" my database and log, will this work as a backup?
Right now I'm doing a full backup every night, but we DO have such software
installed that's backing up the rest of our systems live onto offsite
storage. I consider this to be much "safer", and if we can use this on our
SQL Server as well, I would rest better.
Maury|||Maury
You will find that most sites use the native SQL Server backup to back the
databases up to disk and then use something like Legato or Backup exec to
copy them from disk to offsite storage.
There are several reasons for doing it this way. Certainly most of the
backup programs did not work very well with SQL Server in older versions. It
was always a bit hit of miss if you could actually restore your backups. Mos
t
of the main tools do know have SQL Server speciffic modules now, which means
they are better at backing up SQL Server.
Using the native SQL Server backup means no version problem issues, which
can be useful.
By using the SQL Server backup to disk you have an easily accessable version
of the backup. This can be useful if you need to restore from it or want to
copy it to another server for support purposes.
The bottom line is that most people use native SQL Server backup to disk and
then a third party tool, because in most cases it is the best way to do it.
Regards
John
"Maury Markowitz" wrote:

> I consider the documentation on this topic somewhat confusing, so I figure
d
> I'd ask here.
> If I use any one of the common network backup utilities, and tell it to
> "live backup" my database and log, will this work as a backup?
> Right now I'm doing a full backup every night, but we DO have such softwar
e
> installed that's backing up the rest of our systems live onto offsite
> storage. I consider this to be much "safer", and if we can use this on our
> SQL Server as well, I would rest better.
> Maury|||"John Bandettini" wrote:

> There are several reasons for doing it this way. Certainly most of the
> backup programs did not work very well with SQL Server in older versions.
Can you be more specific on this particular issue? We're currently running
SS2k, is this one of the "older versions" you mention? Do you know what sort
of problems should be expected in these cases?
Technically it seems there shouldn't be a problem. Writes to the logs should
be flushed through immediately, which is what I would suspect COULD cause a
problem.
Maury