backup restored to an MSDE

Does Microsoft officially support restoring a standard edition DB to the MSDE?
Thanks, and a link would be great....
burt_king@.yahoo.com
Sure, this works.
|||I know it works; is it officially supported?
burt_king@.yahoo.com
"Jens" wrote:

> Sure, this works.
>
|||Sure, thats a normal upgrade / upscaling path.
HTH, jens Suessmeyer.
|||I can't find any Microsoft resource --Books on line or other-- that agrees
with your statement that it's supported. Can you point me to a resource?
burt_king@.yahoo.com
"Jens" wrote:

> Sure, thats a normal upgrade / upscaling path.
> HTH, jens Suessmeyer.
>

backup restored to an MSDE

Does Microsoft officially support restoring a standard edition DB to the MSD
E?
Thanks, and a link would be great....
burt_king@.yahoo.comSure, this works.|||I know it works; is it officially supported?
--
burt_king@.yahoo.com
"Jens" wrote:

> Sure, this works.
>|||Sure, thats a normal upgrade / upscaling path.
HTH, jens Suessmeyer.|||I can't find any Microsoft resource --Books on line or other-- that agrees
with your statement that it's supported. Can you point me to a resource?
burt_king@.yahoo.com
"Jens" wrote:

> Sure, thats a normal upgrade / upscaling path.
> HTH, jens Suessmeyer.
>sql

backup restored to an MSDE

Does Microsoft officially support restoring a standard edition DB to the MSDE?
Thanks, and a link would be great....
--
burt_king@.yahoo.comSure, this works.|||I know it works; is it officially supported?
--
burt_king@.yahoo.com
"Jens" wrote:
> Sure, this works.
>|||Sure, thats a normal upgrade / upscaling path.
HTH, jens Suessmeyer.|||I can't find any Microsoft resource --Books on line or other-- that agrees
with your statement that it's supported. Can you point me to a resource?
burt_king@.yahoo.com
"Jens" wrote:
> Sure, thats a normal upgrade / upscaling path.
> HTH, jens Suessmeyer.
>

Backup problems

Hi all !!
Last week I made a backup of a database since we need this database t
be restored on a different server.
To do the backup I used Backup tool included in SQL (right click o
database / All tasks / Backup Database ). Backup was made with defaul
options (appent to media checked as well).
The backup file was 1,7 GB size and I decided to compress it in orde
to being able to burn a CD and send it, the compress file was 250 MB s
I burnt a CD with compress database and sent it.
My problem is when the guys where the other server is allocate
restored the backup they could do it but didn't recover the newes
version of the database, they recover an older version from 3 week
ago.
I wonder if this problem could be caused because I didn't chec
overwrite media option (and I check append to media option) from SQ
backup tool or this can be caused for any other reason like the
weren't able to recover it properly or that I should use othe
different tool from SQL one.
Thanks in advance !
Migue
-
Miguel Ange
----
Posted via http://www.webservertalk.co
----
View this thread: http://www.webservertalk.com/message200843.htmMost likely you have several backups on the backup file. You can use RESTORE HEADERONLY to check this and then
the FILE option when you perform the restore.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Miguel Angel" <Miguel.Angel.15dlii@.mail.webservertalk.com> wrote in message
news:Miguel.Angel.15dlii@.mail.webservertalk.com...
> Hi all !!
> Last week I made a backup of a database since we need this database to
> be restored on a different server.
> To do the backup I used Backup tool included in SQL (right click on
> database / All tasks / Backup Database ). Backup was made with default
> options (appent to media checked as well).
> The backup file was 1,7 GB size and I decided to compress it in order
> to being able to burn a CD and send it, the compress file was 250 MB so
> I burnt a CD with compress database and sent it.
> My problem is when the guys where the other server is allocated
> restored the backup they could do it but didn't recover the newest
> version of the database, they recover an older version from 3 weeks
> ago.
> I wonder if this problem could be caused because I didn't check
> overwrite media option (and I check append to media option) from SQL
> backup tool or this can be caused for any other reason like they
> weren't able to recover it properly or that I should use other
> different tool from SQL one.
> Thanks in advance !
> Miguel
>
> --
> Miguel Angel
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message200843.html
>

Backup problems

Hi all !!
Last week I made a backup of a database since we need this database to be re
stored on a different server.
To do the backup I used Backup tool included in SQL (right click on databas
e / All tasks / Backup Database ). Backup was made with default options (ap
pent to media checked as well).
The backup file was 1,7 GB size and I decided to compress it in order to bei
ng able to burn a CD and send it, the compress file was 250 MB so I burnt a
CD with compress database and sent it.
My problem is when the guys where the other server is allocated restored the
backup they could do it but didn't recover the newest version of the databa
se, they recover an older version from 3 weeks ago.
I wonder if this problem could be caused because I didn't check overwrite me
dia option (and I check append to media option) from SQL backup tool or this
can be caused for any other reason like they weren't able to recover it pro
perly or that I should use other different tool from SQL one.
Thanks in advance !
MiguelMost likely you have several backups on the backup file. You can use RESTORE
HEADERONLY to check this and then
the FILE option when you perform the restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Miguel Angel" <Miguel.Angel.15dlii@.mail.webservertalk.com> wrote in message
news:Miguel.Angel.15dlii@.mail.webservertalk.com...
> Hi all !!
> Last week I made a backup of a database since we need this database to
> be restored on a different server.
> To do the backup I used Backup tool included in SQL (right click on
> database / All tasks / Backup Database ). Backup was made with default
> options (appent to media checked as well).
> The backup file was 1,7 GB size and I decided to compress it in order
> to being able to burn a CD and send it, the compress file was 250 MB so
> I burnt a CD with compress database and sent it.
> My problem is when the guys where the other server is allocated
> restored the backup they could do it but didn't recover the newest
> version of the database, they recover an older version from 3 weeks
> ago.
> I wonder if this problem could be caused because I didn't check
> overwrite media option (and I check append to media option) from SQL
> backup tool or this can be caused for any other reason like they
> weren't able to recover it properly or that I should use other
> different tool from SQL one.
> Thanks in advance !
> Miguel
>
> --
> Miguel Angel
> ---
> Posted via http://www.webservertalk.com
> ---
> View this thread: http://www.webservertalk.com/message200843.html
>

Backup problems

Hi all !!
Last week I made a backup of a database since we need this database to
be restored on a different server.
To do the backup I used Backup tool included in SQL (right click on
database / All tasks / Backup Database ). Backup was made with default
options (appent to media checked as well).
The backup file was 1,7 GB size and I decided to compress it in order
to being able to burn a CD and send it, the compress file was 250 MB so
I burnt a CD with compress database and sent it.
My problem is when the guys where the other server is allocated
restored the backup they could do it but didn't recover the newest
version of the database, they recover an older version from 3 weeks
ago.
I wonder if this problem could be caused because I didn't check
overwrite media option (and I check append to media option) from SQL
backup tool or this can be caused for any other reason like they
weren't able to recover it properly or that I should use other
different tool from SQL one.
Thanks in advance !
Miguel
Miguel Angel
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message200843.html
Most likely you have several backups on the backup file. You can use RESTORE HEADERONLY to check this and then
the FILE option when you perform the restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Miguel Angel" <Miguel.Angel.15dlii@.mail.webservertalk.com> wrote in message
news:Miguel.Angel.15dlii@.mail.webservertalk.com...
> Hi all !!
> Last week I made a backup of a database since we need this database to
> be restored on a different server.
> To do the backup I used Backup tool included in SQL (right click on
> database / All tasks / Backup Database ). Backup was made with default
> options (appent to media checked as well).
> The backup file was 1,7 GB size and I decided to compress it in order
> to being able to burn a CD and send it, the compress file was 250 MB so
> I burnt a CD with compress database and sent it.
> My problem is when the guys where the other server is allocated
> restored the backup they could do it but didn't recover the newest
> version of the database, they recover an older version from 3 weeks
> ago.
> I wonder if this problem could be caused because I didn't check
> overwrite media option (and I check append to media option) from SQL
> backup tool or this can be caused for any other reason like they
> weren't able to recover it properly or that I should use other
> different tool from SQL one.
> Thanks in advance !
> Miguel
>
> --
> Miguel Angel
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message200843.html
>

Backup into Standby mode...

Does anyone know if it is possible to backup a functional database, and then place it in standby mode capable of having logs restored on it? (SQL 2k on Win2k)

In a nutshell, this is what I am trying to do. Server A is live in production. Server B is new shiny powerful server waiting to become production. I want to backup our 60 gig DB copy it from A to B. Restore it on B. Stop SQL on A, copy new transaction logs to B, apply them, rename B to A and bring it up as the new production server. Now, here's the problem. I want to make the old A into the warm spare. To do this it has to be in standby mode ready to accept transaction logs. Restoring onto oldA is not an option because it is taking around 10 hours to do it, and we would be without a back up for that time. Not good.

So anyone know if this is possible, or have a better migration plan?The migration scheme you described sounds like an approach I've (sucessfully) used for DB machine migrations where downtime must be minimized.|||You can use the Log Shipping process to accomplish this project.
For more detail instruction on this, please refer to BOL. I can give you an example of restore a Full backup (from Server A) to Server B:

restore database MYDB
from disk='\\servername\bak\MYDB.BAK'
with MOVE MYDB_data' to 'H:\MSSQL\data\MYDB_Data.MDF',
MOVE MYDB_log' to 'E:\MSSQL\log\MYDB_log.LDF',
REPLACE, RESTART, STANDBY ='T:\MYDB_undo',
STATS

After this, the translog from Server A will automatically copied &
restore into Server B. After successfully setup the server B as a hot standby, you then switch the role between the 2 servers.|||We experienced many problems when changed that way, mainly because SQL refused to be renamed! (I'm talking abour SQL7, maybe SQL2K works better)

Also, we have problems with IP addresses, mirroring, SP's, etc...

What about replication?
I saw very impressive results in LANs and WANs.|||The first approach worked for us as well (though we had plenty of down time and only a 10GB database to work with.

Some notes:
1. Renaming with SQL 2K did not seem to be a problem for us, except for the Jobs. When we renamed the servers, the jobs retained the original name and were thus considered to be "owned" by another server. I could not enable them, disable them, delete them or otherwise modify them. I eventually went into the sysjobs table in MSDB and modified the "owner"

2. If you have a lot of users, watch out. It's easy to migrate the logins over using the DTS transfer package, but you then have to "link" the logins on the new server to the permissions they had on the old server. I'll dig through my notes, but there is a process to do this (and it's not well documented in the SQL 2000 log shipping in SQL BOL).

3. The Log Shipping concept proposed by someone else should also work well for you. Very well in fact. You still have to watch out for jobs, DTS packages and the logins, but if you need a minimum amount of downtime, then I would strongly consider this approach. It may not work from SQL 7 to SQL 2K.

Good luck,

Hugh Scott

Originally posted by Cesar Fraustro
We experienced many problems when changed that way, mainly because SQL refused to be renamed! (I'm talking abour SQL7, maybe SQL2K works better)

Also, we have problems with IP addresses, mirroring, SP's, etc...

What about replication?
I saw very impressive results in LANs and WANs.|||Good points there hmscott. Here is how I propose to get around those very issues...

1. We are planning on scripting out all the jobs prior to the move, and then recreating them once we hit the new machine.

2. I have scripted out the sysxlogins table to a table I created on another server. doing this, it is pretty simple to link the logins to the apporpriate database, which, when restored, has all the permissions associated with it.

3. I am still researching logshipping. We use a home grown solution that works pretty well, so we'll have to look at em both and go from there.

Finally, for anyone that is interested, it is possible to bring a database back up into standby mode by doing a backup log with standby command. you then apply that log you just backed up using a restore log with standby and from there, you can apply transaction logs.

Thanks for all your help.

Backup in SQL 7.0 and restored in SQL 2000

Hello: I have made backup of a data base in SQL 7.0 and I have been able it to recover in a SQL 2000 without problems, can this generate some kind to me of later problem in this restored database?You should be fine with the method you have chosen but you may have problems with logins. Also, double-check to make sure that customized objects have been restored as well - e.g. stored procedures, jobs, dts scripts ...

Check out the following article:

article1 (http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q246133&ID=KB;EN-US;Q246133&)

For an excellent in-depth article discussing moving databases from 7 to 2000, check out the following article - part 2 is more specific:

article2 (http://www.sqlteam.com/item.asp?ItemID=9066)|||For the login issues run SP_CHANGE_USERS_LOGIN REPORT which reports orphaned users and run WITH AUTO_FIX to fix the logins, refer to BOL for more information.

HTH

Backup file vs. Database file

Hi,
I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
file that I've restored to a database. That database is now a whopping 185
GB. Can someone explain to me why this database is so large?
Thank you in advance,
DeeI just wanted to clarify that I've restored the backup file to a brand new
database.
"bpdee" wrote:
> Hi,
> I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> file that I've restored to a database. That database is now a whopping 185
> GB. Can someone explain to me why this database is so large?
> Thank you in advance,
> Dee|||Here is some more information when I ran the sp_spaceused stored procedure.
database_name database_size unallocated space
-- -- --
DecisionStore 181474.19 MB 174091.16 MB
reserved data index_size unused
-- -- -- --
5774368 KB 5540816 KB 158864 KB 74688 KB
"bpdee" wrote:
> Hi,
> I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> file that I've restored to a database. That database is now a whopping 185
> GB. Can someone explain to me why this database is so large?
> Thank you in advance,
> Dee|||Because you had a lot of free space when you took backup of that database. When you restore, SQL
Server will put back each page in the original location (page address of the database file). Because
of this, each file has to be at least the size it was when you performed the backup.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"bpdee" <bpdee@.discussions.microsoft.com> wrote in message
news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
> Hi,
> I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> file that I've restored to a database. That database is now a whopping 185
> GB. Can someone explain to me why this database is so large?
> Thank you in advance,
> Dee|||Thanks, Tibor! I've tried using DBCC SHRINKFILE and DBCC SHRINKDATABASE on
the database and I can't seem to lessen the filesize of the mdf file. Do you
have any suggestion on how to do this?
"Tibor Karaszi" wrote:
> Because you had a lot of free space when you took backup of that database. When you restore, SQL
> Server will put back each page in the original location (page address of the database file). Because
> of this, each file has to be at least the size it was when you performed the backup.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
> > Hi,
> >
> > I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> > file that I've restored to a database. That database is now a whopping 185
> > GB. Can someone explain to me why this database is so large?
> >
> > Thank you in advance,
> > Dee
>|||Fragmentation can be one reason. First step would be to investigate the information that DBCC
SHRINKFILE returns (documented in Books Online).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"bpdee" <bpdee@.discussions.microsoft.com> wrote in message
news:2EDC0D8F-2FA6-4FE4-A5FB-0A088F476FBC@.microsoft.com...
> Thanks, Tibor! I've tried using DBCC SHRINKFILE and DBCC SHRINKDATABASE on
> the database and I can't seem to lessen the filesize of the mdf file. Do you
> have any suggestion on how to do this?
> "Tibor Karaszi" wrote:
>> Because you had a lot of free space when you took backup of that database. When you restore, SQL
>> Server will put back each page in the original location (page address of the database file).
>> Because
>> of this, each file has to be at least the size it was when you performed the backup.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
>> news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
>> > Hi,
>> >
>> > I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
>> > file that I've restored to a database. That database is now a whopping 185
>> > GB. Can someone explain to me why this database is so large?
>> >
>> > Thank you in advance,
>> > Dee
>>|||This is the information that I get.
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
-- -- -- -- -- --
8 1 23005464 128 719344 719336
"Tibor Karaszi" wrote:
> Fragmentation can be one reason. First step would be to investigate the information that DBCC
> SHRINKFILE returns (documented in Books Online).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> news:2EDC0D8F-2FA6-4FE4-A5FB-0A088F476FBC@.microsoft.com...
> > Thanks, Tibor! I've tried using DBCC SHRINKFILE and DBCC SHRINKDATABASE on
> > the database and I can't seem to lessen the filesize of the mdf file. Do you
> > have any suggestion on how to do this?
> >
> > "Tibor Karaszi" wrote:
> >
> >> Because you had a lot of free space when you took backup of that database. When you restore, SQL
> >> Server will put back each page in the original location (page address of the database file).
> >> Because
> >> of this, each file has to be at least the size it was when you performed the backup.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> >> news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
> >> > Hi,
> >> >
> >> > I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> >> > file that I've restored to a database. That database is now a whopping 185
> >> > GB. Can someone explain to me why this database is so large?
> >> >
> >> > Thank you in advance,
> >> > Dee
> >>
> >>
>|||So you currently have 23005464 pages and according to DBCC SHRINKFILE you should be able to get down
to 719336 pages. I can only assume that there's some page high in the file which can't be moved,
like for instance some page for a service broker table or similar. I suggest you start by Googling
on this issue and see if you can find other with same symptoms (data file, not log). I do recall
vaguely some reasons why shrinkfile might not cut it, like system table pages high, possibly LOB
pages and similar, but I can't recall details, I'm afraid... :-(
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"bpdee" <bpdee@.discussions.microsoft.com> wrote in message
news:A16F4176-E110-432E-92F7-680289AA9651@.microsoft.com...
> This is the information that I get.
> DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
> -- -- -- -- -- --
> 8 1 23005464 128 719344 719336
> "Tibor Karaszi" wrote:
>> Fragmentation can be one reason. First step would be to investigate the information that DBCC
>> SHRINKFILE returns (documented in Books Online).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
>> news:2EDC0D8F-2FA6-4FE4-A5FB-0A088F476FBC@.microsoft.com...
>> > Thanks, Tibor! I've tried using DBCC SHRINKFILE and DBCC SHRINKDATABASE on
>> > the database and I can't seem to lessen the filesize of the mdf file. Do you
>> > have any suggestion on how to do this?
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> Because you had a lot of free space when you took backup of that database. When you restore,
>> >> SQL
>> >> Server will put back each page in the original location (page address of the database file).
>> >> Because
>> >> of this, each file has to be at least the size it was when you performed the backup.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
>> >> news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
>> >> > file that I've restored to a database. That database is now a whopping 185
>> >> > GB. Can someone explain to me why this database is so large?
>> >> >
>> >> > Thank you in advance,
>> >> > Dee
>> >>
>> >>|||No problem, Tibor. Thank again so much for all of your help!
"Tibor Karaszi" wrote:
> So you currently have 23005464 pages and according to DBCC SHRINKFILE you should be able to get down
> to 719336 pages. I can only assume that there's some page high in the file which can't be moved,
> like for instance some page for a service broker table or similar. I suggest you start by Googling
> on this issue and see if you can find other with same symptoms (data file, not log). I do recall
> vaguely some reasons why shrinkfile might not cut it, like system table pages high, possibly LOB
> pages and similar, but I can't recall details, I'm afraid... :-(
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> news:A16F4176-E110-432E-92F7-680289AA9651@.microsoft.com...
> > This is the information that I get.
> >
> > DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages
> > -- -- -- -- -- --
> > 8 1 23005464 128 719344 719336
> >
> > "Tibor Karaszi" wrote:
> >
> >> Fragmentation can be one reason. First step would be to investigate the information that DBCC
> >> SHRINKFILE returns (documented in Books Online).
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> >> news:2EDC0D8F-2FA6-4FE4-A5FB-0A088F476FBC@.microsoft.com...
> >> > Thanks, Tibor! I've tried using DBCC SHRINKFILE and DBCC SHRINKDATABASE on
> >> > the database and I can't seem to lessen the filesize of the mdf file. Do you
> >> > have any suggestion on how to do this?
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> Because you had a lot of free space when you took backup of that database. When you restore,
> >> >> SQL
> >> >> Server will put back each page in the original location (page address of the database file).
> >> >> Because
> >> >> of this, each file has to be at least the size it was when you performed the backup.
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://sqlblog.com/blogs/tibor_karaszi
> >> >>
> >> >>
> >> >> "bpdee" <bpdee@.discussions.microsoft.com> wrote in message
> >> >> news:7717DF9A-0730-49D0-8962-7859ED7F0854@.microsoft.com...
> >> >> > Hi,
> >> >> >
> >> >> > I'm running SQL Server 2005 on Windows 2003 Server. I have a 6 GB backup
> >> >> > file that I've restored to a database. That database is now a whopping 185
> >> >> > GB. Can someone explain to me why this database is so large?
> >> >> >
> >> >> > Thank you in advance,
> >> >> > Dee
> >> >>
> >> >>
> >>
>