I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
Thanks in advance for any help.ITDUDE27,
Are you using SharePoint and Small Business Server? If so, here are a
couple of links:
http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
I do have one weird thought: it sounds as if the file location for the files
in the database does not match the actual file locations of the mdf and/or
ldf. Did you use the MOVE option during the RESTORE in order to position
the files properly?
Other than that, I have no really useful suggestions.
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> Thanks in advance for any help.
>|||Thanks Russ.
I'am running SP on SBS 2003. my Live sharepoint site is running fine and I
was able to install SP 2.0 on another server and it came up fine. I trying to
restore a copy of the live db as test and that is what is causing the error.
I had seen the second link you refered too, it was not help full. The point
of this exercise is to restore the sp database using Enterprize manager and
query it and then map it as my SP content database.
I've tried the move command using osql with no success. I think you are
absoluty correct about the Move, I'm just not having any luck, which ever way
I restore the SP db I get the same message.
Thanks in advance for any other feedback.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||Russell,
Can you comfirm the syntax for me.
Current location: N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak from other server
New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak'
WITH
MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_new.mdf'
MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_log.ldf'
Thanks in advance.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||ITDUDE27,
Syntax looks correct, but the code does not match your spec. Compare:
N:\Program Files\Microsoft SQL Server\MSSQL\Data
N:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\avalanche_new.mdf
If N:\ is a network drive that is not a supported configuration for SQL
Server databases. You will need to place the database files on locally
attached storage or on your SAN.
And, of course, I assume that the 'northwind%' logical names are correct.
I also usually specify a couple of things that should not be necessary in my
RESTORE command. Habit, you know, but I include the options:
RECOVERY, REPLACE
FWIW,
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:F7C1965F-448C-44F1-8DEF-9860E15E1A86@.microsoft.com...
> Russell,
> Can you comfirm the syntax for me.
> Current location: N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak from other server
> New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
>
> RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak'
> WITH
> MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_new.mdf'
> MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_log.ldf'
> Thanks in advance.
>
> "Russell Fields" wrote:
>> ITDUDE27,
>> Are you using SharePoint and Small Business Server? If so, here are a
>> couple of links:
>> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
>> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
>> I do have one weird thought: it sounds as if the file location for the
>> files
>> in the database does not match the actual file locations of the mdf
>> and/or
>> ldf. Did you use the MOVE option during the RESTORE in order to position
>> the files properly?
>> Other than that, I have no really useful suggestions.
>> RLF
>> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
>> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
>> > I'm restoring a database on another server, the restore from disk goes
>> > through successfully, until I try to click on tables or views I get the
>> > message below:
>> >
>> > Error 954: Database 'dbname' has invalid schema
>> >
>> > Thanks in advance for any help.
>> >
>> >
>>
Showing posts with label sql2000. Show all posts
Showing posts with label sql2000. Show all posts
Thursday, March 29, 2012
Friday, March 9, 2012
Error 5149: Not enough disk space
Newbie question:
Importing a 25,000,000 record .csv file into SQL2000 fails
with a disk space error. I go into sql enterprise manager
to increase the size of the database and it will only let
me go to about 4000 MB. I need about 30GIG. At 5000 MB
enterprise manager says:
Error 5149: ModifyFile encountered operating system error
112 (There is not enough space on the disk while
attempting to expand physical file).
I have 50GIG free on that disk.
What am I doing wrong'"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote in message
news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
> Newbie question:
> Importing a 25,000,000 record .csv file into SQL2000 fails
> with a disk space error. I go into sql enterprise manager
> to increase the size of the database and it will only let
> me go to about 4000 MB. I need about 30GIG. At 5000 MB
> enterprise manager says:
> Error 5149: ModifyFile encountered operating system error
> 112 (There is not enough space on the disk while
> attempting to expand physical file).
> I have 50GIG free on that disk.
> What am I doing wrong'
It's possible that you are either running out of transaction log space (on
either the target database) or on tempdb -- check that you have enabled
database file autogrow, or have size the database large enough to hold the
imported data (my preference).
If this fails, you may want to watch the server os page file (performance
monitor) in case the os is swapping out memory to disk...
Steve|||I'm getting this error when I go into properties of the
database, Data Files tab, Space Allocated (MB) column. I
try to change the entry from 4000 to 5000, and it gives me
the 5149 error. I'm not trying to import the data, yet.
When I tried before to import the data it failed with a
message the Primary File Group ran out of space. So I
deleted the database, made a new one, and tried to set the
data file size, to no avail.
The database is set to grow automatically, and it grows
unlimited.
>--Original Message--
>"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote
in message
>news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
>> Newbie question:
>> Importing a 25,000,000 record .csv file into SQL2000
fails
>> with a disk space error. I go into sql enterprise
manager
>> to increase the size of the database and it will only
let
>> me go to about 4000 MB. I need about 30GIG. At 5000 MB
>> enterprise manager says:
>> Error 5149: ModifyFile encountered operating system
error
>> 112 (There is not enough space on the disk while
>> attempting to expand physical file).
>> I have 50GIG free on that disk.
>> What am I doing wrong'
>It's possible that you are either running out of
transaction log space (on
>either the target database) or on tempdb -- check that
you have enabled
>database file autogrow, or have size the database large
enough to hold the
>imported data (my preference).
>If this fails, you may want to watch the server os page
file (performance
>monitor) in case the os is swapping out memory to disk...
>Steve
>
>.
>|||Could it be the version of SQL? I have the personal
edition?
>--Original Message--
>Newbie question:
>Importing a 25,000,000 record .csv file into SQL2000
fails
>with a disk space error. I go into sql enterprise manager
>to increase the size of the database and it will only let
>me go to about 4000 MB. I need about 30GIG. At 5000 MB
>enterprise manager says:
>Error 5149: ModifyFile encountered operating system error
>112 (There is not enough space on the disk while
>attempting to expand physical file).
>I have 50GIG free on that disk.
>What am I doing wrong'
>.
>
Importing a 25,000,000 record .csv file into SQL2000 fails
with a disk space error. I go into sql enterprise manager
to increase the size of the database and it will only let
me go to about 4000 MB. I need about 30GIG. At 5000 MB
enterprise manager says:
Error 5149: ModifyFile encountered operating system error
112 (There is not enough space on the disk while
attempting to expand physical file).
I have 50GIG free on that disk.
What am I doing wrong'"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote in message
news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
> Newbie question:
> Importing a 25,000,000 record .csv file into SQL2000 fails
> with a disk space error. I go into sql enterprise manager
> to increase the size of the database and it will only let
> me go to about 4000 MB. I need about 30GIG. At 5000 MB
> enterprise manager says:
> Error 5149: ModifyFile encountered operating system error
> 112 (There is not enough space on the disk while
> attempting to expand physical file).
> I have 50GIG free on that disk.
> What am I doing wrong'
It's possible that you are either running out of transaction log space (on
either the target database) or on tempdb -- check that you have enabled
database file autogrow, or have size the database large enough to hold the
imported data (my preference).
If this fails, you may want to watch the server os page file (performance
monitor) in case the os is swapping out memory to disk...
Steve|||I'm getting this error when I go into properties of the
database, Data Files tab, Space Allocated (MB) column. I
try to change the entry from 4000 to 5000, and it gives me
the 5149 error. I'm not trying to import the data, yet.
When I tried before to import the data it failed with a
message the Primary File Group ran out of space. So I
deleted the database, made a new one, and tried to set the
data file size, to no avail.
The database is set to grow automatically, and it grows
unlimited.
>--Original Message--
>"Ben Silvert" <anonymous@.discussions.microsoft.com> wrote
in message
>news:1be701c39fc7$d4faa450$3101280a@.phx.gbl...
>> Newbie question:
>> Importing a 25,000,000 record .csv file into SQL2000
fails
>> with a disk space error. I go into sql enterprise
manager
>> to increase the size of the database and it will only
let
>> me go to about 4000 MB. I need about 30GIG. At 5000 MB
>> enterprise manager says:
>> Error 5149: ModifyFile encountered operating system
error
>> 112 (There is not enough space on the disk while
>> attempting to expand physical file).
>> I have 50GIG free on that disk.
>> What am I doing wrong'
>It's possible that you are either running out of
transaction log space (on
>either the target database) or on tempdb -- check that
you have enabled
>database file autogrow, or have size the database large
enough to hold the
>imported data (my preference).
>If this fails, you may want to watch the server os page
file (performance
>monitor) in case the os is swapping out memory to disk...
>Steve
>
>.
>|||Could it be the version of SQL? I have the personal
edition?
>--Original Message--
>Newbie question:
>Importing a 25,000,000 record .csv file into SQL2000
fails
>with a disk space error. I go into sql enterprise manager
>to increase the size of the database and it will only let
>me go to about 4000 MB. I need about 30GIG. At 5000 MB
>enterprise manager says:
>Error 5149: ModifyFile encountered operating system error
>112 (There is not enough space on the disk while
>attempting to expand physical file).
>I have 50GIG free on that disk.
>What am I doing wrong'
>.
>
Wednesday, March 7, 2012
error 3624 severity 20 SQL server was stopped often
hi~~
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>
Subscribe to:
Posts (Atom)