In All Programs/Microsoft SQL Server - Switch is something called SQL Server
Upgrade Wizard. I have no idea what that does, so I thought I'd start it up
and see what happens.
What happens is that I get an error message saying that my virtual memory is
too low, and should be set at the physical memory + 16 MB. My physical
memory is 512 MB and virtual memory is 767 MB, so the error message is
wrong.
Can someone explain what's going on? What does that thing do, anyway?It's designed to upgrade old 6.5 server configuration and databases to SQL
Server 2K. Are you trying to upgrade old 6.5 server configurations and
databases?
"Paul Pedersen" <no-reply@.swen.com> wrote in message
news:efe2nK%23UFHA.584@.TK2MSFTNGP15.phx.gbl...
> In All Programs/Microsoft SQL Server - Switch is something called SQL
> Server Upgrade Wizard. I have no idea what that does, so I thought I'd
> start it up and see what happens.
> What happens is that I get an error message saying that my virtual memory
> is too low, and should be set at the physical memory + 16 MB. My physical
> memory is 512 MB and virtual memory is 767 MB, so the error message is
> wrong.
> Can someone explain what's going on? What does that thing do, anyway?
>
>|||No, just exploring.
But why does it refuse to run?
"Michael C#" <xyz@.abcdef.com> wrote in message
news:Ofrfe.20738$o32.19288@.fe09.lga...
> It's designed to upgrade old 6.5 server configuration and databases to SQL
> Server 2K. Are you trying to upgrade old 6.5 server configurations and
> databases?
> "Paul Pedersen" <no-reply@.swen.com> wrote in message
> news:efe2nK%23UFHA.584@.TK2MSFTNGP15.phx.gbl...
>|||Maybe because it can't find any 6.5 databases/server configurations? You'd
have to look up the specific reason in the MSKB. Doesn't sound like it's
worth the effort - considering you don't have any 6.5 databases to upgrde
anyway...
"Paul Pedersen" <no-reply@.swen.com> wrote in message
news:uTlQzpEVFHA.2616@.TK2MSFTNGP14.phx.gbl...
> No, just exploring.
> But why does it refuse to run?
>
> "Michael C#" <xyz@.abcdef.com> wrote in message
> news:Ofrfe.20738$o32.19288@.fe09.lga...
>
Showing posts with label bogus. Show all posts
Showing posts with label bogus. Show all posts
Monday, March 19, 2012
Bogus ''out of disk space'' error message
When running SQLEVAL.EXE, I'm getting an error message when the installation wizard finished 'reading contents of the package' reading:
There is not enough space on C:\ to extract this package.
Having checked the requirements http://www.microsoft.com/sql/editions/developer/sysreqs.mspx, the free disk space on my c:\ is 45.42Gb.
Any ideas?
See: http://blogs.msdn.com/nikop/archive/2005/03/13/394797.aspxBogus 'out of disk space' error message
When running SQLEVAL.EXE, I'm getting an error message when the installation wizard finished 'reading contents of the package' reading:
There is not enough space on C:\ to extract this package.
Having checked the requirements http://www.microsoft.com/sql/editions/developer/sysreqs.mspx, the free disk space on my c:\ is 45.42Gb.
Any ideas?
See: http://blogs.msdn.com/nikop/archive/2005/03/13/394797.aspxBogus "Invalid object name" error
Hi all,
I'm posting this so it'll be archived in the great google
repository, and hopefully be useful to someone. I spent awhile
troubleshooting what turned out to be a completely misleading error
arising from a simple typo in a query. Here's the crux:
create table foo (id int)
The command(s) completed successfully.
insert foo ('id') values (1)
Server: Msg 208, Level 16, State 3, Line 1
Invalid object name 'foo'.
insert foo (id) values (1)
(1 row(s) affected)
drop table foo
The command(s) completed successfully.
--
My first insert statement has incorrect single quotes around the
column name, which for some reason leads to the error shown.
Unfortunately, my real-life problem was much more convoluted, and
this took a couple hours to debug. I hope this post saves someone
time someday! This is on SQLServer 2000 w/SP3a.
Cheers...It probably won't when it happens, but it may for people who read it :)
These strange types of error messages have been around as long as time
itself. Thanks for posting stuff like this!
--
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Jerry" <leavemealone@.nowhere.com> wrote in message
news:Xns9660740FD7089leavemealonenowhere
c@.207.225.159.8...
> Hi all,
> I'm posting this so it'll be archived in the great google
> repository, and hopefully be useful to someone. I spent awhile
> troubleshooting what turned out to be a completely misleading error
> arising from a simple typo in a query. Here's the crux:
> --
> create table foo (id int)
> The command(s) completed successfully.
> insert foo ('id') values (1)
> Server: Msg 208, Level 16, State 3, Line 1
> Invalid object name 'foo'.
> insert foo (id) values (1)
> (1 row(s) affected)
> drop table foo
> The command(s) completed successfully.
> --
> My first insert statement has incorrect single quotes around the
> column name, which for some reason leads to the error shown.
> Unfortunately, my real-life problem was much more convoluted, and
> this took a couple hours to debug. I hope this post saves someone
> time someday! This is on SQLServer 2000 w/SP3a.
> Cheers...
I'm posting this so it'll be archived in the great google
repository, and hopefully be useful to someone. I spent awhile
troubleshooting what turned out to be a completely misleading error
arising from a simple typo in a query. Here's the crux:
create table foo (id int)
The command(s) completed successfully.
insert foo ('id') values (1)
Server: Msg 208, Level 16, State 3, Line 1
Invalid object name 'foo'.
insert foo (id) values (1)
(1 row(s) affected)
drop table foo
The command(s) completed successfully.
--
My first insert statement has incorrect single quotes around the
column name, which for some reason leads to the error shown.
Unfortunately, my real-life problem was much more convoluted, and
this took a couple hours to debug. I hope this post saves someone
time someday! This is on SQLServer 2000 w/SP3a.
Cheers...It probably won't when it happens, but it may for people who read it :)
These strange types of error messages have been around as long as time
itself. Thanks for posting stuff like this!
--
----
Louis Davidson - http://spaces.msn.com/members/drsql/
SQL Server MVP
"Jerry" <leavemealone@.nowhere.com> wrote in message
news:Xns9660740FD7089leavemealonenowhere
c@.207.225.159.8...
> Hi all,
> I'm posting this so it'll be archived in the great google
> repository, and hopefully be useful to someone. I spent awhile
> troubleshooting what turned out to be a completely misleading error
> arising from a simple typo in a query. Here's the crux:
> --
> create table foo (id int)
> The command(s) completed successfully.
> insert foo ('id') values (1)
> Server: Msg 208, Level 16, State 3, Line 1
> Invalid object name 'foo'.
> insert foo (id) values (1)
> (1 row(s) affected)
> drop table foo
> The command(s) completed successfully.
> --
> My first insert statement has incorrect single quotes around the
> column name, which for some reason leads to the error shown.
> Unfortunately, my real-life problem was much more convoluted, and
> this took a couple hours to debug. I hope this post saves someone
> time someday! This is on SQLServer 2000 w/SP3a.
> Cheers...
Subscribe to:
Posts (Atom)