Question about restoring a database

All,
I have many DTS packages pulling data from production
servers to reporting servers. This is going to be changed
so that the production servers push the data to the
reporting servers.
The production server DBA wants to periodically make a
full backup of the databases, "zip" them, and FTP them to
the reporting servers. On the reporting servers, the "zip"
files will be un-zipped and the databases will be
restored. The databases are scattered over half the US.
Most of the tables, triggers, stored procedures, views,
users, etc. in the copied databases are not needed for our
reporting. I would like to be able to drop these objects
from the reporting server databases immediately after they
are restored. Doing so will free up significant amounts of
hard drive space.
My biggest concern is that dropping objects from a
database will cause problems when attempting a restore? Is
this concern valid?
TIA,
Mike> My biggest concern is that dropping objects from a
> database will cause problems when attempting a restore? Is
> this concern valid?
You mean that next time you will restore the database? No, that will not
cause problems. One thing, though. Top free up space after dropping the
object you need to shrink the files. Because of this, before the next
restore, you either need to delete the database first, or use the REPLACE
parameter in the RESTORE command.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:057001c3a97b$cec6ea40$a401280a@.phx.gbl...
> All,
> I have many DTS packages pulling data from production
> servers to reporting servers. This is going to be changed
> so that the production servers push the data to the
> reporting servers.
> The production server DBA wants to periodically make a
> full backup of the databases, "zip" them, and FTP them to
> the reporting servers. On the reporting servers, the "zip"
> files will be un-zipped and the databases will be
> restored. The databases are scattered over half the US.
> Most of the tables, triggers, stored procedures, views,
> users, etc. in the copied databases are not needed for our
> reporting. I would like to be able to drop these objects
> from the reporting server databases immediately after they
> are restored. Doing so will free up significant amounts of
> hard drive space.
> My biggest concern is that dropping objects from a
> database will cause problems when attempting a restore? Is
> this concern valid?
> TIA,
> Mike
>
>sql

Question about querying database with select statement in SQL Server 2005

In the sql server 2005, why do I need to perform querying as followed
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.
Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Question about querying database with select statement in SQL Server 2005

In the sql server 2005, why do I need to perform querying as followed
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Question about DIFFERENTIAL backups

Our production backup schedule is, FULL backup once a month and a DIFFERENTIAL backup every day.

We are starting the FULL and DIFFERENTIAL backups using something similar to

FULL Backup
backup database @.DB to disk = @.BackupFile

DIFFERENTIAL backup
backup database @.DB to disk = @.BackupFile WITH DIFFERENTIAL

A full backup was done on 10/6 and the DB size was 48GB. Since then we have been doing DIFFERENTIAL backups. I recently looked at the DIFFERENTIAL backup directory and found something I think is interesting.

10/07/2005 04:00 AM 8,604,160 prodDB_Diff_200510070400.BAK
10/08/2005 04:00 AM 1,144,320 prodDB_Diff_200510080400.BAK
10/09/2005 04:00 AM 1,134,080 prodDB_Diff_200510090400.BAK
10/10/2005 04:00 AM 21,185,024 prodDB_Diff_200510100400.BAK
10/11/2005 04:00 AM 7,119,360 prodDB_Diff_200510110400.BAK
10/12/2005 04:00 AM 163,669,504 prodDB_Diff_200510120400.BAK
10/13/2005 04:00 AM 14,743,040 prodDB_Diff_200510130400.BAK
10/14/2005 04:00 AM 120,875,520 prodDB_Diff_200510140400.BAK
10/15/2005 04:00 AM 1,216,000 prodDB_Diff_200510150400.BAK
10/16/2005 04:00 AM 5,139,968 prodDB_Diff_200510160400.BAK
10/17/2005 04:00 AM 4,277,760 prodDB_Diff_200510170400.BAK
10/18/2005 04:00 AM 2,778,624 prodDB_Diff_200510180400.BAK
10/19/2005 04:01 AM 750,575,104 prodDB_Diff_200510190400.BAK

My understanding of DIFFERENTIAL backups from books online is
"Specifies the database or file backup should consist only of the portions of the database or file changed since the last full backup"

MY Question:
Assuming I am understanding this correctly, all DIFFERENTIAL backups are independent of one another. If a failure happens, all I have to do is restore the latest FULL backup and then
restore the latest DIFFERENTIAL backup.

So, I would think the sizes of the backup files should be in ASCENDING order. Why is the size of the backup file from 10/15/2005 (1,216,000 bytes) smaller than the backup file from 10/14/2005 (120,875,520 bytes).

Assuming a crash happens on 10/15 5AM, I would restore the full backup from 10/6 and then restore the DIFF. backup from 10/15 4AM (Which will apply approx.. 1,216,000 bytes of data). So where has the data in the backup file from 10/14/2005 gone (120,875,520 bytes)?

ThanksНou mistaken
Look for keyword "Differential Database Backups"

"A differential database backup records only the data that has changed since the last database backup."
Draw attention - "last database backup". No full backup.|||From BOL:

DIFFERENTIAL

Specifies the database or file backup should consist only of the portions of the database or file changed since the last full backup. A differential backup usually takes up less space than a full backup. Use this option so that all individual log backups since the last full backup do not need to be applied. For more information, see Differential Database Backups and File Differential Backups.

Note During a full database or differential backup, SQL Server backs up enough of the transaction log to produce a consistent database when the database is restored.

Are you doing a lot of updates during the time it takes to do the backups?|||Thanks so much for your response..

Right, your quote from BOL is exactly what I read. It has FULL backup written all over it.

Are you sure it is
""A differential database backup records only the data that has changed since the last database backup."

rather than what BOL says it is

"Specifies the database or file backup should consist only of the portions of the database or file changed since the last full backup"

I wouldn't say lots of updates but the DB is being used.|||You have the right idea about restoring the database in your situation. Just 2 restores, and one recovery, no matter what day you go down.

I am also puzzled by the wild size differences in there. This isn't something strange like the destination of a log-shipping instance, is it? I could see full backups on the source database causing this behavior.

Question about DBCC Shrinkfile

I've got a SQL Server database that was restored from production (SQL Server 2000) to a development instance (SQL Server 2005). After the restore I deleted about 90% of the user data, by copying 10% to a temp table, truncating, and re-inserting the data.

I tried to shrink the files, but the biggest file won't shrink. Running sp_helpfile, I see:

name fileid filename filegroup size maxsize growth usage
MyDB_Data 1 M:\Data\MyDB_Data.MDF PRIMARY 190504832 KB Unlimited 1024000 KB data only

So the file is about 181 GB, but I know that it's mostly empty space. Running sp_spaceused gives me 142531.77 MB unallocated space, which I know is mostly in the MDF file. When I run DBCC Shrinkfile(MyDB_Data, 170000), the command runs successfully but there is no change in the file size. Does anyone have any idea why the file won't shrink? I've seen this in log files before but never in data files.

Results from shrinkfile:

DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
5 1 23813104 2560000 5686656 5686656

Dylan Peters

shrinkdb only shrinks the database down at most to its original created size. That means if the db file can only shrink down to the MinimumSize.|||

oj wrote:

shrinkdb only shrinks the database down at most to its original created size. That means if the db file can only shrink down to the MinimumSize.

In this case the minimum size is 2560000 pages or 10000 MB, just 10 GB. The current file size is 23813104 pages or 93019 MB, and the pages used comes out to 22214 MB. So I should be able to get it down to about 22 GB in theory. The BOL for shrinkfile says it can be used to shrink the file to less than its original created size, but I'm not going below 10 GB anyway.

Dylan Peters

|||No. You cannot shrink it less than the original created size.

http://msdn2.microsoft.com/en-us/library/ms190488.aspx

"The database cannot be made smaller than the minimum size of the database. The

minimum size is the size specified when the database is originally created, or

the last size explicitly set by using a file size changing operation such as

DBCC SHIRNKFILE or ALTER DATABASE. For example, if a database is originally

created with a size of 10 MB in size and grows to 100 MB, the smallest the

database can be reduced to is 10 MB, even if all the data in the database has

been deleted."

But that is not your current problem. My guess is that you have removed a bunch of blob but you can't reclaim the space. See the following kb for detail.

http://support.microsoft.com/default.aspx/kb/324432

Question about Back ups

I have a production server that has a lot of data changes through out the
day. I do one full back up at night and do hourly log back ups through out
the major part of the day.
My question is when I do the full back up does it back up the log as well
and does it purge the data in the log? Also, when I do hourly log back ups
should I append the most recent hourly log back up or overwrite it? Not sure
if the log purges when you do a back up?
Thanks for your help?
-ChrisChris
My question is when I do the full back up does it back up the log as well
> and does it purge the data in the log?
Yes , it does backup log file as well, but it does not "clear" the file ( I
mean ,commited tranactions(inactive portions) are still in)
>Also, when I do hourly log back ups
> should I append the most recent hourly log back up or overwrite it?
Well , you could by using backup log file WITH INIT option, however , an
advantage of this option is that in terms of database's crach you don't need
to apply hundred of logs to get the database "healthy", on the other hand
if your last full database is corrupted/lost , you are still will ne able to
restore a backup from the two/three weeks ago and apply all log files
without loosing the data, actually it is possible because whole databse
backup does not truncate log files
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2992A4FC-E1DB-4108-9DD8-3B4E515CCD43@.microsoft.com...
>I have a production server that has a lot of data changes through out the
> day. I do one full back up at night and do hourly log back ups through out
> the major part of the day.
> My question is when I do the full back up does it back up the log as well
> and does it purge the data in the log? Also, when I do hourly log back ups
> should I append the most recent hourly log back up or overwrite it? Not
> sure
> if the log purges when you do a back up?
> Thanks for your help?
> -Chris
>|||On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:

>I have a production server that has a lot of data changes through out the
>day. I do one full back up at night and do hourly log back ups through out
>the major part of the day.
>My question is when I do the full back up does it back up the log as well
>and does it purge the data in the log?
Hi Chris,
See Uri's reply.

> Also, when I do hourly log back ups
>should I append the most recent hourly log back up or overwrite it? Not sur
e
>if the log purges when you do a back up?
Don't overwrite it. The log file is purged after a log backup. If you do
a full backup at midnight and log backups on the full hour, recovering
from a crash at 4:15 PM requires you to restore
- The last full backup,
- All log backups since midnight up to 4 PM
- The log backup up to 4:15 PM (taken after the crash)
You should only overwrite log backups from before the last full backup,
and you might consider keeping them around for some time as well since
this would be an extra safeguard in case the full backup would be
corrupted.
Hugo Kornelis, SQL Server MVP|||Hugo
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
I meant to use WITH INIT option once in two/three weeks and NOT after every
LOG file that the OP does.
I fully agree with you that we don't need to owerwrite log file backups
after each backup (hourly in his case)
"Hugo Kornelis" <hugo@.perFact.REMOVETHIS.info.INVALID> wrote in message
news:3mk8721gfi3lhd36khnhoh4ul8cne0h2u3@.
4ax.com...
> On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
>
> Hi Chris,
> See Uri's reply.
>
> Don't overwrite it. The log file is purged after a log backup. If you do
> a full backup at midnight and log backups on the full hour, recovering
> from a crash at 4:15 PM requires you to restore
> - The last full backup,
> - All log backups since midnight up to 4 PM
> - The log backup up to 4:15 PM (taken after the crash)
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
> --
> Hugo Kornelis, SQL Server MVP|||So if the log file is purged after the log back up then I want to append the
last back up until I do a full back up. Is there a way to overwrite once,
after the full back up so my log back up file is not growing to an enormous
size?
"Hugo Kornelis" wrote:

> On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
>
> Hi Chris,
> See Uri's reply.
>
> Don't overwrite it. The log file is purged after a log backup. If you do
> a full backup at midnight and log backups on the full hour, recovering
> from a crash at 4:15 PM requires you to restore
> - The last full backup,
> - All log backups since midnight up to 4 PM
> - The log backup up to 4:15 PM (taken after the crash)
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
> --
> Hugo Kornelis, SQL Server MVP
>|||> So if the log file is purged after the log back up then I want to append then">
> last back up until I do a full back up.
What about backup generations?

> Is there a way to overwrite once,
> after the full back up so my log back up file is not growing to an enormou
s
> size?
You have to code that functionality. Or use maintenance plans. Nothing built
-in at the TSQL level.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:407FDDF9-0D12-4F6E-8E4C-364743B6DC65@.microsoft.com...[vbcol=seagreen]
> So if the log file is purged after the log back up then I want to append t
he
> last back up until I do a full back up. Is there a way to overwrite once,
> after the full back up so my log back up file is not growing to an enormou
s
> size?
>
> "Hugo Kornelis" wrote:
>|||Great Thanks for all of your help !!
"Uri Dimant" wrote:

> Hugo
> I meant to use WITH INIT option once in two/three weeks and NOT after ever
y
> LOG file that the OP does.
> I fully agree with you that we don't need to owerwrite log file backups
> after each backup (hourly in his case)
>
>
>
> "Hugo Kornelis" <hugo@.perFact.REMOVETHIS.info.INVALID> wrote in message
> news:3mk8721gfi3lhd36khnhoh4ul8cne0h2u3@.
4ax.com...
>
>

Question about Back ups

I have a production server that has a lot of data changes through out the
day. I do one full back up at night and do hourly log back ups through out
the major part of the day.
My question is when I do the full back up does it back up the log as well
and does it purge the data in the log? Also, when I do hourly log back ups
should I append the most recent hourly log back up or overwrite it? Not sure
if the log purges when you do a back up?
Thanks for your help?
-ChrisChris
My question is when I do the full back up does it back up the log as well
> and does it purge the data in the log?
Yes , it does backup log file as well, but it does not "clear" the file ( I
mean ,commited tranactions(inactive portions) are still in)
>Also, when I do hourly log back ups
> should I append the most recent hourly log back up or overwrite it?
Well , you could by using backup log file WITH INIT option, however , an
advantage of this option is that in terms of database's crach you don't need
to apply hundred of logs to get the database "healthy", on the other hand
if your last full database is corrupted/lost , you are still will ne able to
restore a backup from the two/three weeks ago and apply all log files
without loosing the data, actually it is possible because whole databse
backup does not truncate log files
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2992A4FC-E1DB-4108-9DD8-3B4E515CCD43@.microsoft.com...
>I have a production server that has a lot of data changes through out the
> day. I do one full back up at night and do hourly log back ups through out
> the major part of the day.
> My question is when I do the full back up does it back up the log as well
> and does it purge the data in the log? Also, when I do hourly log back ups
> should I append the most recent hourly log back up or overwrite it? Not
> sure
> if the log purges when you do a back up?
> Thanks for your help?
> -Chris
>|||On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
>I have a production server that has a lot of data changes through out the
>day. I do one full back up at night and do hourly log back ups through out
>the major part of the day.
>My question is when I do the full back up does it back up the log as well
>and does it purge the data in the log?
Hi Chris,
See Uri's reply.
> Also, when I do hourly log back ups
>should I append the most recent hourly log back up or overwrite it? Not sure
>if the log purges when you do a back up?
Don't overwrite it. The log file is purged after a log backup. If you do
a full backup at midnight and log backups on the full hour, recovering
from a crash at 4:15 PM requires you to restore
- The last full backup,
- All log backups since midnight up to 4 PM
- The log backup up to 4:15 PM (taken after the crash)
You should only overwrite log backups from before the last full backup,
and you might consider keeping them around for some time as well since
this would be an extra safeguard in case the full backup would be
corrupted.
--
Hugo Kornelis, SQL Server MVP|||Hugo
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
I meant to use WITH INIT option once in two/three weeks and NOT after every
LOG file that the OP does.
I fully agree with you that we don't need to owerwrite log file backups
after each backup (hourly in his case)
"Hugo Kornelis" <hugo@.perFact.REMOVETHIS.info.INVALID> wrote in message
news:3mk8721gfi3lhd36khnhoh4ul8cne0h2u3@.4ax.com...
> On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
>>I have a production server that has a lot of data changes through out the
>>day. I do one full back up at night and do hourly log back ups through out
>>the major part of the day.
>>My question is when I do the full back up does it back up the log as well
>>and does it purge the data in the log?
> Hi Chris,
> See Uri's reply.
>> Also, when I do hourly log back ups
>>should I append the most recent hourly log back up or overwrite it? Not
>>sure
>>if the log purges when you do a back up?
> Don't overwrite it. The log file is purged after a log backup. If you do
> a full backup at midnight and log backups on the full hour, recovering
> from a crash at 4:15 PM requires you to restore
> - The last full backup,
> - All log backups since midnight up to 4 PM
> - The log backup up to 4:15 PM (taken after the crash)
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
> --
> Hugo Kornelis, SQL Server MVP|||So if the log file is purged after the log back up then I want to append the
last back up until I do a full back up. Is there a way to overwrite once,
after the full back up so my log back up file is not growing to an enormous
size?
"Hugo Kornelis" wrote:
> On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
> >I have a production server that has a lot of data changes through out the
> >day. I do one full back up at night and do hourly log back ups through out
> >the major part of the day.
> >
> >My question is when I do the full back up does it back up the log as well
> >and does it purge the data in the log?
> Hi Chris,
> See Uri's reply.
> > Also, when I do hourly log back ups
> >should I append the most recent hourly log back up or overwrite it? Not sure
> >if the log purges when you do a back up?
> Don't overwrite it. The log file is purged after a log backup. If you do
> a full backup at midnight and log backups on the full hour, recovering
> from a crash at 4:15 PM requires you to restore
> - The last full backup,
> - All log backups since midnight up to 4 PM
> - The log backup up to 4:15 PM (taken after the crash)
> You should only overwrite log backups from before the last full backup,
> and you might consider keeping them around for some time as well since
> this would be an extra safeguard in case the full backup would be
> corrupted.
> --
> Hugo Kornelis, SQL Server MVP
>|||> So if the log file is purged after the log back up then I want to append the
> last back up until I do a full back up.
What about backup generations?
> Is there a way to overwrite once,
> after the full back up so my log back up file is not growing to an enormous
> size?
You have to code that functionality. Or use maintenance plans. Nothing built-in at the TSQL level.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:407FDDF9-0D12-4F6E-8E4C-364743B6DC65@.microsoft.com...
> So if the log file is purged after the log back up then I want to append the
> last back up until I do a full back up. Is there a way to overwrite once,
> after the full back up so my log back up file is not growing to an enormous
> size?
>
> "Hugo Kornelis" wrote:
>> On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
>> >I have a production server that has a lot of data changes through out the
>> >day. I do one full back up at night and do hourly log back ups through out
>> >the major part of the day.
>> >
>> >My question is when I do the full back up does it back up the log as well
>> >and does it purge the data in the log?
>> Hi Chris,
>> See Uri's reply.
>> > Also, when I do hourly log back ups
>> >should I append the most recent hourly log back up or overwrite it? Not sure
>> >if the log purges when you do a back up?
>> Don't overwrite it. The log file is purged after a log backup. If you do
>> a full backup at midnight and log backups on the full hour, recovering
>> from a crash at 4:15 PM requires you to restore
>> - The last full backup,
>> - All log backups since midnight up to 4 PM
>> - The log backup up to 4:15 PM (taken after the crash)
>> You should only overwrite log backups from before the last full backup,
>> and you might consider keeping them around for some time as well since
>> this would be an extra safeguard in case the full backup would be
>> corrupted.
>> --
>> Hugo Kornelis, SQL Server MVP|||Great Thanks for all of your help !!
"Uri Dimant" wrote:
> Hugo
> > You should only overwrite log backups from before the last full backup,
> > and you might consider keeping them around for some time as well since
> > this would be an extra safeguard in case the full backup would be
> > corrupted.
> I meant to use WITH INIT option once in two/three weeks and NOT after every
> LOG file that the OP does.
> I fully agree with you that we don't need to owerwrite log file backups
> after each backup (hourly in his case)
>
>
>
> "Hugo Kornelis" <hugo@.perFact.REMOVETHIS.info.INVALID> wrote in message
> news:3mk8721gfi3lhd36khnhoh4ul8cne0h2u3@.4ax.com...
> > On Wed, 24 May 2006 05:06:02 -0700, Chris wrote:
> >
> >>I have a production server that has a lot of data changes through out the
> >>day. I do one full back up at night and do hourly log back ups through out
> >>the major part of the day.
> >>
> >>My question is when I do the full back up does it back up the log as well
> >>and does it purge the data in the log?
> >
> > Hi Chris,
> >
> > See Uri's reply.
> >
> >> Also, when I do hourly log back ups
> >>should I append the most recent hourly log back up or overwrite it? Not
> >>sure
> >>if the log purges when you do a back up?
> >
> > Don't overwrite it. The log file is purged after a log backup. If you do
> > a full backup at midnight and log backups on the full hour, recovering
> > from a crash at 4:15 PM requires you to restore
> > - The last full backup,
> > - All log backups since midnight up to 4 PM
> > - The log backup up to 4:15 PM (taken after the crash)
> >
> > You should only overwrite log backups from before the last full backup,
> > and you might consider keeping them around for some time as well since
> > this would be an extra safeguard in case the full backup would be
> > corrupted.
> >
> > --
> > Hugo Kornelis, SQL Server MVP
>
>

Question about Antivirus install to db server.

Hi,
SA want install the Antivirus software on production database server, he
said he will exclude those files extension with mdf, ldf, and ndf from the
VirusScan engine to avoid performance issues. My question is how about the
bak extension files? Do I also need exclude backup files?
Regards!
ChenNo
You need backup file only when you are restoring database. SQL Server
does not use it for any other operations. It may be possible your other
non sql files also contains .bak extension. So its better to check it.
Regards
Amish Shah

Question about Antivirus install to db server.

Hi,
SA want install the Antivirus software on production database server, he
said he will exclude those files extension with mdf, ldf, and ndf from the
VirusScan engine to avoid performance issues. My question is how about the
bak extension files? Do I also need exclude backup files?
Regards!
ChenNo
You need backup file only when you are restoring database. SQL Server
does not use it for any other operations. It may be possible your other
non sql files also contains .bak extension. So its better to check it.
Regards
Amish Shah