"Overflow!" error when Upsizing from Access

Hi
I've just installed MSDE 2000 Release A on WinXP Pro. All seems okay, but when I try to upsize an Access Database, I get a message box saying "Overflow!".
Any ideas on what I'm doing wrong? I'm new to SQL Server
Cheers
Dan
It depends on which version of Access you are using -- see
http://support.microsoft.com/default...;en-us;q294407 for
the Access 2002 upsizing whitepaper -- there's a link to the A2000 one
if you're using that.
--Mary
On Sun, 1 Aug 2004 08:37:02 -0700, "Dan Nash" <dan@.musoswire.co.uk>
wrote:

>Hi
>I've just installed MSDE 2000 Release A on WinXP Pro. All seems okay, but when I try to upsize an Access Database, I get a message box saying "Overflow!".
>Any ideas on what I'm doing wrong? I'm new to SQL Server
>Cheers
>
>Dan
|||Mary,
Thanks, am downloading that now. Forgot to mention I'm using Access 2000.
One question though.. when you install, what's the default login you would use? I used the SAPWD switch to create my password, but what's the Login ID for a default instance? May seem like a silly question, but it might be what's causing my problems!
Cheers
Dan
"Mary Chipman" wrote:

> It depends on which version of Access you are using -- see
> http://support.microsoft.com/default...;en-us;q294407 for
> the Access 2002 upsizing whitepaper -- there's a link to the A2000 one
> if you're using that.
> --Mary
> On Sun, 1 Aug 2004 08:37:02 -0700, "Dan Nash" <dan@.musoswire.co.uk>
> wrote:
>
>
|||I'm a little rusty on A2k, but as I recall you have to use a SQL login
and password with the upwiz, not integrated security (the whitepaper
should discuss this). It's a valid login that you create. FWIW,
upgrading to Access 2003 is highly recommended if you're going to keep
an Access FE to a SQLS BE. A2k was released *before* SQLS 2k, and
there have been many improvements and bug fixes since then.
--Mary
On Sun, 1 Aug 2004 13:49:03 -0700, "Dan Nash" <dan@.musoswire.co.uk>
wrote:
[vbcol=seagreen]
>Mary,
>Thanks, am downloading that now. Forgot to mention I'm using Access 2000.
>One question though.. when you install, what's the default login you would use? I used the SAPWD switch to create my password, but what's the Login ID for a default instance? May seem like a silly question, but it might be what's causing my problems!
>Cheers
>
>Dan
>"Mary Chipman" wrote:

"Not enough Storage"

When I tried to save a stored proedure (in SQL Server 2005 Express), I got a
n
error saying "The operation could not be completed. Not enough storage is
available to complete this operation."
Any idea what is causing this error to pop up? I still have about 4GB disk
space left.
Thanks.SQL Express has a 4GB limit on the database size so if you're at that limit
you are out of space no matter how much disk space is left.
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
"Swami" <Swami@.discussions.microsoft.com> wrote in message
news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||My whole MSSQL folder is only 148 MB and my particular database in question
is only 2MB in size. I actually have very little data...about 7-8 tables
which are mostly empty and about 25 stored procedures, each of them quite
short. Any ideas?
Thanks.
"Roger Wolter[MSFT]" wrote:

> SQL Express has a 4GB limit on the database size so if you're at that limi
t
> you are out of space no matter how much disk space is left.
> --
> 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
> "Swami" <Swami@.discussions.microsoft.com> wrote in message
> news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
>
>|||Well, one guess is you might have choosen the option
Do not autogrow
right click on database -> properties -> datafiles
check - Automatically grow file.
and also
maximum file size -> unrestricted file growth.
Do the same in log files. And see.
Hope this helps.
And I believe this is your test database. (and not production :)|||What tool are you using to create the stored procedure? You might try
saving the proc script to a file and creating with the SQLCMD.EXE
command-line utility.
Hope this helps.
Dan Guzman
SQL Server MVP
"Swami" <Swami@.discussions.microsoft.com> wrote in message
news:E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||this message indicated a bug referenced in sql server 2000 if you are using
lookups...
try your error message with google
Nicolas Guinet
"Swami" <Swami@.discussions.microsoft.com> a crit dans le message de news:
E6536E4F-31BE-4609-9DFC-FFCC5C6A1CD2@.microsoft.com...
> When I tried to save a stored proedure (in SQL Server 2005 Express), I got
> an
> error saying "The operation could not be completed. Not enough storage is
> available to complete this operation."
> Any idea what is causing this error to pop up? I still have about 4GB
> disk
> space left.
> Thanks.|||You may want to check out this link too.
http://support.microsoft.com/defaul...;166840&sd=tech