Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts

Sunday, March 25, 2012

Database size question

I have a small application that I've developed using MSDE (2K). I'm
going to put this in to production by setting up a new computer and it
seems that Server 2005 Express edition will be adequate for our needs.
I want to check that the size of the databases I'm using are less than
4GB. How do I do that? I've looked around in SQL Server Enterprise
Manager but I don't see file sizes shown anywhere.
In Query Analyzer, try this:
EXECUTE sp_spaceused
In Enterprise Mangler, right click on the database, choose [Properties]. The
file size is in the middle of the page on the [General] tab,
Also, you can use Windows Explorer to view the database file. (It's not a
precise measure, but it's close.)
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Martin" <martinvalley@.comcast.net> wrote in message
news:2jvbl2h28n9ac4fc2usdi44g3kpa2gv40l@.4ax.com...
>I have a small application that I've developed using MSDE (2K). I'm
> going to put this in to production by setting up a new computer and it
> seems that Server 2005 Express edition will be adequate for our needs.
> I want to check that the size of the databases I'm using are less than
> 4GB. How do I do that? I've looked around in SQL Server Enterprise
> Manager but I don't see file sizes shown anywhere.
|||Thanks, Arnie - I don't know why I couldn't find that
My db's are all in the single-digit MB size, so I guess that the 4GB
limit of the Express version won't be an issue. And of course, if it
ever becomes an issue, we just have to upgrade.
Thanks again.
On Sat, 11 Nov 2006 09:10:03 -0800, "Arnie Rowland" <arnie@.1568.com>
wrote:

>In Query Analyzer, try this:
>EXECUTE sp_spaceused
>In Enterprise Mangler, right click on the database, choose [Properties]. The
>file size is in the middle of the page on the [General] tab,
>Also, you can use Windows Explorer to view the database file. (It's not a
>precise measure, but it's close.)
|||The maximum size of an MSDE database is 2GB so you can be sure your
databases are under 4GB
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Martin" <martinvalley@.comcast.net> wrote in message
news:2jvbl2h28n9ac4fc2usdi44g3kpa2gv40l@.4ax.com...
>I have a small application that I've developed using MSDE (2K). I'm
> going to put this in to production by setting up a new computer and it
> seems that Server 2005 Express edition will be adequate for our needs.
> I want to check that the size of the databases I'm using are less than
> 4GB. How do I do that? I've looked around in SQL Server Enterprise
> Manager but I don't see file sizes shown anywhere.

Wednesday, March 7, 2012

Database restore error

I've been trying to restore a database from a .bak file, but I receive the
next error message:
RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013)
An internal consistency error occurred. Contact Technical Support for
assistance. [SQLSTATE 42000] (Error 3270). The step failed.
Any idea what's this?
Thanks
Sounds like the backup file could be bad. Try executing a
restore headeronly to see if you get any errors when trying
to read the header - and what information is reported for
what is in the backup file if it executes without errors.
-Sue
On Fri, 3 Nov 2006 13:51:02 -0800, alejandro
<alejandro@.discussions.microsoft.com> wrote:

>I've been trying to restore a database from a .bak file, but I receive the
>next error message:
>RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013)
>An internal consistency error occurred. Contact Technical Support for
>assistance. [SQLSTATE 42000] (Error 3270). The step failed.
>Any idea what's this?
>Thanks
|||Hi,
I had a similar issue before and that caused because Database backup was not
fully completed. Verify the source database server for
enough hard disk space. I recommend you to take a full database backup and
try restore...
As far as I know you can do much with corrupted backup file...
Thanks
Hari
"alejandro" <alejandro@.discussions.microsoft.com> wrote in message
news:8E712F6C-EC6A-4E7C-9BF5-50B70557E3B8@.microsoft.com...
> I've been trying to restore a database from a .bak file, but I receive the
> next error message:
> RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013)
> An internal consistency error occurred. Contact Technical Support for
> assistance. [SQLSTATE 42000] (Error 3270). The step failed.
> Any idea what's this?
> Thanks
|||Hari Prasad wrote:
[vbcol=seagreen]
> Hi,
> I had a similar issue before and that caused because Database backup was not
> fully completed. Verify the source database server for
> enough hard disk space. I recommend you to take a full database backup and
> try restore...
> As far as I know you can do much with corrupted backup file...
> Thanks
> Hari
>
> "alejandro" <alejandro@.discussions.microsoft.com> wrote in message
> news:8E712F6C-EC6A-4E7C-9BF5-50B70557E3B8@.microsoft.com...
check validity of your backup using
restore verifyonly from disk = <backup path>
look at BOL for verfiying backups
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/9c0a9c0b-64ba-4d3d-95d5-e09fb05d6154.htm
Regards
Amish Shah
http://shahamishm.tripod.com

Database Restore Causes Log Full

Hi,
I've 2 SQL Server, SQL1 as Primary and SQL2 as Stand-By Server. Database
size is about 5 GB.
I want to restore full and T-logs on SQL2, so my SQL1 Recovery model is set
to Full.
As I don't have off-peak hours, I can not detach/attach database and move it
to SQL2. once a day, I need to move a full backup from SQL1 to SQL2. There's
no problem in backup and copying it to SQL2, but when I want to restore it on
SQL2, restore progress starts and finishes (as I see in sql logs that restore
is finished successfuly) but in "recovery is checkpointing database ..."
step, my database log file starts to grow, it grows until my log become full
and sql get into errors.
in this stage, I can not "backup log" (probably because it's in checkpoiting
process).
Also I tried to "backup and shrink log" in SQL1 before Full Backup, to have
minimum log size, but still after restoring on SQL1, when restore progress
bar is still visible and it's on 100% position, log file on SQL2 starts to
grow...
I suspect that the problem might be because of Full Recovery Model in SQL1
during Full Backup, but because of T-Logs I need this recovery model.
How can I restore my full backup in this case?!!
Best Regards,
Pierre.
Hi
http://www.sql-server-performance.co...g_shipping.asp
"Pierre" <Pierre@.discussions.microsoft.com> wrote in message
news:EB57ED5A-ADE7-4ACC-898A-1B524B4A3AED@.microsoft.com...
> Hi,
> I've 2 SQL Server, SQL1 as Primary and SQL2 as Stand-By Server. Database
> size is about 5 GB.
> I want to restore full and T-logs on SQL2, so my SQL1 Recovery model is
> set
> to Full.
> As I don't have off-peak hours, I can not detach/attach database and move
> it
> to SQL2. once a day, I need to move a full backup from SQL1 to SQL2.
> There's
> no problem in backup and copying it to SQL2, but when I want to restore it
> on
> SQL2, restore progress starts and finishes (as I see in sql logs that
> restore
> is finished successfuly) but in "recovery is checkpointing database ..."
> step, my database log file starts to grow, it grows until my log become
> full
> and sql get into errors.
> in this stage, I can not "backup log" (probably because it's in
> checkpoiting
> process).
> Also I tried to "backup and shrink log" in SQL1 before Full Backup, to
> have
> minimum log size, but still after restoring on SQL1, when restore progress
> bar is still visible and it's on 100% position, log file on SQL2 starts to
> grow...
> I suspect that the problem might be because of Full Recovery Model in SQL1
> during Full Backup, but because of T-Logs I need this recovery model.
> How can I restore my full backup in this case?!!
> Best Regards,
> Pierre.
|||Hi Uri,
Thanks for URL, the restore query in this article was:
RESTORE DATABASE database_name
FROM DISK = 'g:\mssql7\backup\database_name\database_name_back up_device.bak'
WITH
DBO_ONLY,
REPLACE,
STANDBY = 'g:\mssql7\backup\database_name\undo_database_name .ldf',
MOVE 'logical_name' TO 'h:\mssql7\data\database_name.mdf',
MOVE 'logical_name' TO 'f:\mssql7\log\database_name_log.ldf'
I checked it up, what option of this command will help me overcome this
problem?
What's difference between this command and restore wizard that I'm using
currently and get me to this problem?
Regards,
Pierre.
"Uri Dimant" wrote:

> Hi
> http://www.sql-server-performance.co...g_shipping.asp
>
>
>
> "Pierre" <Pierre@.discussions.microsoft.com> wrote in message
> news:EB57ED5A-ADE7-4ACC-898A-1B524B4A3AED@.microsoft.com...
>
>
|||Do you need the db in STANDBY mode?, if not, then use NORECOVERY option
instead, so can then restore the transaction log.

> STANDBY = 'g:\mssql7\backup\database_name\undo_database_name .ldf',
...
NORECOVERY,
...
AMB
"Pierre" wrote:
[vbcol=seagreen]
> Hi Uri,
> Thanks for URL, the restore query in this article was:
> RESTORE DATABASE database_name
> FROM DISK = 'g:\mssql7\backup\database_name\database_name_back up_device.bak'
> WITH
> DBO_ONLY,
> REPLACE,
> STANDBY = 'g:\mssql7\backup\database_name\undo_database_name .ldf',
> MOVE 'logical_name' TO 'h:\mssql7\data\database_name.mdf',
> MOVE 'logical_name' TO 'f:\mssql7\log\database_name_log.ldf'
> I checked it up, what option of this command will help me overcome this
> problem?
> What's difference between this command and restore wizard that I'm using
> currently and get me to this problem?
>
> Regards,
> Pierre.
> "Uri Dimant" wrote:
|||Dear Alejandro,
At this time, I just want to restore my full backup on secondary server
(which growing log file causes restore wizard to fail), then if with STANDBY
options restore succeeded, I'll use NONRECOVERY to be able to restore my
t-logs.
Regards,
Pierre.
"Alejandro Mesa" wrote:
[vbcol=seagreen]
> Do you need the db in STANDBY mode?, if not, then use NORECOVERY option
> instead, so can then restore the transaction log.
>
> ...
> NORECOVERY,
> ...
>
> AMB
> "Pierre" wrote:
|||Hi Again,
restore database db_name with standby ... was successfull and restore
compeleted (database became readonly). at this time I dont have any t-log
backups, and I want to bring this server online, as I suspect I should run
"restore database db_name with recovery" , but when I run this query log file
starts to grow and will become full...
why running "with recovery" fills my log file?! How can I make my database
operational?
Regards,
Pierre.
"Pierre" wrote:
[vbcol=seagreen]
> Dear Alejandro,
> At this time, I just want to restore my full backup on secondary server
> (which growing log file causes restore wizard to fail), then if with STANDBY
> options restore succeeded, I'll use NONRECOVERY to be able to restore my
> t-logs.
> Regards,
> Pierre.
> "Alejandro Mesa" wrote: