Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 scripting error

Author  Topic 

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2004-06-25 : 10:17:17
I'm trying to script a SQL server 7 database using the tool in EM. Every time I try I get error 220 Arithmetic overflow error for data type smallint, value = 65535.

It's quite clearly correct in that it is out of range, what I don't understand is why and what I can do to resolve this error

Many thanks in advance

steve


Steve no function beer well without

Kristen
Test

22859 Posts

Posted - 2004-06-25 : 12:20:44
Script the tables etc. in smaller batches perhaps?

Restore a backup [Oops, you don't have access to those do you ] onto a SQL 2000 box and try scripting that?

Try the SQL 2000 client tools (with latest service pack) against the SQL 7 DB?

Kristen
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2004-06-26 : 19:20:08
LOL, you noticed.

I tried just scripting one table and the same happened, I was using the SQL 2000 client tools (not sure they have the latest service pack though) and intially thought that may have been the problem, but I got the same message with the SQL 7 client tools. I couldn't find any reference on the MS site either.

I'm using Enterprise Mangler, is there another way of creating a script?

thanks

Steve no function beer well without
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2004-06-26 : 19:56:41
sql-dmo
see
http://www.nigelrivett.net/DMOScripting.html
http://www.nigelrivett.net/DMOScriptAllDatabases.html

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2004-06-27 : 05:49:30
> is there another way of creating a script?

Plenty of third party tools (particularly the Entity Modelling type) can do this.

However, you definitely should SP the client tools (and separately download the latest BOL which has a fair few new pages - Search of BOL shows 500, so presumably that's the search results limit ...)

I reckon you'll have the same problem with SQL-DMO because I expect EM is going that route too ... restore onto 2000 and then try has the ADDED benefit that you'll be given access to your database, won't you?!

Kristen
Go to Top of Page

elwoos
Master Smack Fu Yak Hacker

2052 Posts

Posted - 2004-07-01 : 05:34:30
OK this is well beyond a joke now! I've just noticed that if I try to look at the properties of any of my databases I get the same error i.e. Microsoft SQL-DMO (ODBC SQLState: 22003) is in the title bar and the error message is as stated before? Does anyone know what's going on here? I get the same message if I try to create a Copy Database DTS. I've also noticed recently that when I go into Enterprise Mangler I have to do a refresh just to see all the databases, this never happened before.

Does anyone have any clues

Steve no function beer well without
Go to Top of Page
   

- Advertisement -