Im using MS SQL7 as database software ,but now I plan to upgrate SQL7 to SQL2000 . I would like to know that are there any affect on the old database that already use with sql7 after I upgrade to MSSQL2000 ?
Thanks
Does anyone know of a good whitepaper detailing SQL7 to SQL2000 migration?
Thanks, I really appreciate your help.
--Alex
Can anyone tell me of an EASY way to migrate a a database from a SQL 7 server to a SQL 2000 server (two different machines)?
Everything that I have found is only for upgrading SQL 7 to SQL 2000 and this isn't what I need.
Two groups in our company merged into one. The first group has a SQL 7 server that the lease is about to expire on and the second group (mine) has a newer SQL 2000 server that we need to move all of the databases to.
I have tried DTS. It failed. I tried backing up the 7 server and restoring to the new server. It failed.
Are there any other suggestions?
Thanks,
Steve
Hi all
just a quick question for you. has anyone had any problems restoring a SQL7 database to a SQL server 2000?
is there anything special you have to do to get it working?
thanks for your time.
Andrew.
Is there a way I can load a SQL2000 DB backup onto a SQL 7 server? Thanks.
View 1 Replies View RelatedDoes a script that run with sql7 automatically run with sql2000?
I would like to know if my script will run if I change version.
Does anyone know of any reasons(or implications) why sql7 and sql2000 databases SHOULD NOT be on the same box???
Please advise.
Thanks-
Can anyone point me to a white paper/discussion on the issues of gaining access to SQL2000 data from a SQL7 installation? I'm about to upgrade servers from 7 to 2000, but a few of the servers exchange data bi-directionally and the upgrade to both servers at the same time would be problematic; thus the need at some point to get at the SQL2000 data from the SQL7 server.
Thanks,
AL
Somebody knows how to restore a database backup from SQL 7 in a Server with SQL 2000 Installed?
If somebody knows how to do it will save me a lot of work?
Thanks a lot.
Hi folks,
I'm currently on a project that'll move all my SQL7 databases into SQL2000. This is from a SQL7 production box to a new Windows2k SQL2000 box. I'm confused as to the proper way of moving all the objects over. What should i do? Any information. Thank You!
Is it possible to administer both SQL7 & SQL2000 databases from the same console ?? It's fine administering SQL 6.5 & SQL7, as 6.5 had no MMC, but it seems that SQL7 & SQL2000 have the same MMC.
Thanks,
Jazz.
Hi there,
I need to create a copy of a SQL 2000 database in another server which has SQL 7.0 installed. When I do a backup and restore, it gives me the following error :
Server: Msg 3154, Level 16, State 2, Line 1
The backup set holds a backup of a database other than the existing 'inventmast' database.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
It seems to be like a downward compatability issue. Is there any other way to restore a sql2000 db onto sql 7 ??
Thanks
Paul
I'm upgrading a set of databases from SQL7 on one server (A) to SQL2000 on another server (B). I'd like input on the best method for moving the databases over (BCP, restore from BAK, etc), and in particular on moving the list of valid users (with default databases, permissions to databases, etc) and the DTS packages and Agent jobs.
When moving the databases, which are currently in code page 850, I might want to have them convert to the standard Latin-1 of SQL2000, though this isn't critical.
TIA,
Al
I have table with about 2 million rows. Everyday about 18000 rows are inserted. The table contain events for site security system so archiving is neccessary. I would appreicate any help or ideas. Thanks in advance.
View 2 Replies View RelatedI have a SQL Server 2000 box running two databases which was upgraded in error from SQL7.0 Basically we are no longer being given support as SQL2000 is not supported by the suppliers.
I therefore need to downgrade the box to SQL7.0 and was wondering if anyone had any opinions on the best method for doing this. Note that I do have a spare server to host the databases while I rebuild this server ( I am having to do a complete rebuild from scratch for other reasons ).
My thought is to transfer the databases to the spare server, rebuild the first box to SQL 7.0 and then perform a snapshot replication to transfer the data back.
Any thoughts on this would be gratefully received.
I have a backup of a SQL7 DB that i need to restore into SQL 2000. I only have the backup of the DB , i don't have access to the SQL7 server. When ever I try to restore the DB into SQL2000 nothing works, the tables and properties all restore properly and the data is there but i can't retrieve info from it. I'm trying to move a website DB from SQL7 to SQL 2000 for use with Cold Fusion. I know they're is issues with going from 7 to 2000 but i don't know what they are. If anyone could help me with this i would greatly appreciate it. I know I need to do some special steps or changes before it will work in 2000, does anyone know what these are?
Thanks in advance,
B
Hi, guys - looking for a bit of help/advice on moving a database fromSQL 7 to SQL 2000.We've a third party application which currently uses a SQL7 database.This database has a number of views which are owned by userINFORMATION_SCHEMA and are set as system tables. This user doesn'tactually have a login on the SQL server.We've tried the following to recreate the database on SQL2000, butwhatever we try, the views owned by INFORMATION_SCHEMA won't copy overfrom SQL7:(1) We tried the "Copy Database" wizard in SQL2000, but were gettingerrors when trying to actually copy the database (other steps workedfine).(2) We tried a restore to SQL2000 from our Legato Networker backup ofthe SQL7 database, but the views didn't come across.(3) We tried a backup from SQL7 and restore to SQL2000, but got themessage that the backup file contained a database other than the onewe wanted (it didn't - we checked the backup file several times byrestoring it to another SQL7 server).(4) We tried to import/export data from SQL7 to SQL2000, but the viewsowned by INFORMATION_SCHEMA weren't showing to add to the list ofobjects to take across.(5) We created the INFORMATION_SCHEMA login on SQL2000, and tried allrestores again, but still the views wouldn't go across.(6) We generated the SQL for all views in SQL7 and ran these onSQL2000, setting the owner to INFORMATION_SCHEMA, but wasn't surewhere to set the type to "system" (as opposed to "user).We're having problems running the third party application with aconnection to SQL2000, and want to rule out the lack of views, or viewownership, as the problem. Our third party vendor isn't coming upwith any solution in a hurry. Can anyone think of any reason why theviews are coming across when the database is restored to SQL2000?Thanks for your help.
View 1 Replies View RelatedI have setup SQL2000 Personal edition on my notebook.
I cannot connect to an existing SQL7 server on the network anymore. I
used to run SQL7 Desktop edition which ran just fine.
I also noticed that when I start my machine it take about 2 minutes
until the SQL service is started.
Any ideas why this is not working anymore?
Thomas Schoch
Elephant Software AG
Switzerland
How to restore a database dump file (.BAK) that backed up from SQL2000 server to a SQL 7.0 server?Please help.Saiyou
View 1 Replies View RelatedI'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
The following query runs fine on sql 7.0 but it kind of hangs/keeps running without any output on sql server 2000
---------------------
Set @cmd = 'Update ABCD Set
'+@day+'_LB = IsNull(LB,0),
'+@day+'_UT = IsNull(UNIT,0)
From tempData as T
Where T.STORE_NUM = ABCD.STORE_NUM And T.ITM_ID = ABCD.UPC'
execute (@cmd)
------------------------------------
But if we hard code the @day parameter and run the query like this it runs very fast on sql 2000....
Update ABCD Set THIRD_LB = IsNull(LB,0),
THIRD_UT = IsNull(UNIT,0)
From tempData as T
Where T.STORE_NUM = ABCD.STORE_NUM And T.ITM_ID = ABCD.UPC
------------------------------
I have a database on a 6.5 server but wish to upgrade this database to a sql 7 database. But I would like to test this first on another server which is a sql 7 server. Is it possible to restore a 6.5 backup to a SQL server 7.0 server?
Thanks in advance..
Hi all
I would like to know - we are currently running SQL6.0 on NT4 servers. We have 2 x 3rd party programs that runs on the servers, making use of the databases. We don't forsee any changes in the near future.
Question: will it be wise to upgrade to SQL7 anyways, or can we keep the status quo as is ???
Rgds
De Waal
I had a number of jobs which were backing up system and user databases under SQL 7 using SQL ServerAgent. Over the weekend I upgraded SQL 7 to SQL 2K.
All backups work except for one, which gets the following error message: Executed as user: SANDIEGOSvcSQLServer. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
As best as I know SQLSTATE 42000 is an ODBC message indicating a syntax violation or an access violation. I have recreated the maintenance plan in an attempt to rule out a syntax violation. During the upgrade process I did not change the account under which SQL Server Agent runs, so it seems like it should not be an access violation.
Any ideas would be appreciated!!!
Thanks Gary Andrews Andrews_gary_w@solarturbines.com
I have a SQL6.5 sp5a, NT4 sp5, BDC, IE5 server that I have installed SQL7
on. My installation is set to mixed security.
Everytime I try to run the upgrade wizard I get the following error/problem
right after the "Checking 6.x syscomments for corruption and Verifying 6.x
data base logins etc.
Summary of warnings (if any) and choices:
=============================================
The following syscomments entries are invalid on your 6.x SQL Server. It is
recommended that you fix these problems before you continue.
=============================================
********************************
master
********************************
********************************
Inconsistency Report For Database: master.
********************************
dbo.sp_db_upgrade2
Procedure
Occurs 28 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_fallback_activate_svr_db
Procedure
Occurs three times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_password
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_recompile
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_rename
Procedure
Occurs 11 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
=============================================
The following script will be created as upgrade.ini and run into the script
interpreter when you press finish.
=============================================
[Options]
Method=1
Perform a CRC Check=0
Source=CCIDEV
Destination=CCIDEV
Export Server Startup Options=
Import Server Startup Options= -T1808
SQLServer70Path=C:MSSQL7SourcePassword=066ce2f9c0e 4ba
DestinationPassword=00
MasterPath=C:MSSQLDATAMASTER.DAT
VerswitchOldVer=65
Code Page=1252
Override Server Code Page=0
QuotedIdentifiers=0
ObjectDumpPath=c:mssql7upgradeCCIDEV_071399_163117 Ansi Nulls=0
[Tasks]
Export and Import via Named Pipe=0
Marking database upgrade status=0
Export Logins=0
Export Database Owners=0
Import Logins=0
Creating Databases=0
Setting Database Options=0
Export Database Objects=0
Import Database Objects=0
Export SQL Executive Settings=0
Preparing MSDB for Upgrade=0
Import SQL Executive Settings=0
Export Server Settings from Master=0
Modifying Scripts=0
Import Server Settings from Master=0
Preparing SQL-DMO for upgrade=0
[Databases]
006CCIDATA=0
003model=0
005msdb=0
001master=0
I don't find anything about this anywhere except the upgrading to SQL7 white
paper, it mentions that the text for objects must be intact in the
syscomments system table and that logins must exist for every database user,
but that doesn't really tell me how to fix this.
Has any one seen these errors or can point me
to where on Microsoft's site you can now EASILY get KB info for SQL Server
7?
I need some strong points for the management to convince them to upgrade to sql2000 now than waiting for 6 months.
We are currently in process of developing this new product. All development is on sql7. I want to upgrade our database to sql2000 now rather than waiting after the release which might be in another 3 months.
I will be upgrading my SQL7 Servers (SP1) to SQL2000 and NT4 to WIN2000 this year. Unfortunately, I will not be able to get new boxes to do this, so I will have to do the upgrades on the systems I have. Our network people have not yet developed a plan for the WIN2K upgrade of our entire network. I will have to upgrade the SQL Servers before they have their plan together. If I want, I can upgrade the SQL Servers to WIN2K before the rest of the network. Assuming that the WIN2K upgrade and the SQL Server upgrade can not be done at the same time, which would be the better order (and why), upgrading to WIN2K and staying at SQL7 first or upgrading to SQL2000 and staying at NT4? The primary goal is to get the indexed views to improve performance on reports and queries.
Thanks for your input.
Roger
Hi,
I am planning to upgrade my sql7.0 with sp2 to sql2000. Pls anyone give me the steps i need to consider and give me some suggestions.
Thanks!
Kavira
any body tell me if there is an upgrade of sql2000 to sql2005
thanks
Hello,
We're planning to upgrade our OS from Windows2000Svr to Windows2003,my question is,will there be problem on my SQL2000 installed? is there patch needed for the SQL2000 to run in Windows2003 environment?
thanks®ards,
jerico
Hi,
I'm running a VB6 app with MDAC 2.8 on Windows Server 2003 SP1.
I create an ADO recordset with a SELECT statement which returns an empty recordset.
I then add 2 new records to it with AddNew and later perform an UpdateBatch.
Before the SQL upgrade it worked fine but now errors with:
'Cannot convert a char value to money. The char value has incorrect syntax.'
I did a SQL Trace to find out what the Updatebatch was actualling sending to SQL (listed below).
This works fine when I run it on Query Analyser using SQL 2000 but fails on SQL 2005.
I worked out the problem is linked to the columns NewValue and OldValue both are varchar 70.
The first insert has them defined varchar(7) and varchar(1). This insert succeeds, but the second insert has the columns defined as varchar(18) and varchar(12). This one fails (unless they only contains numbers!).
I'm confused.
I've read that sp_executesql has changed for SQL2005.
Any ideas anyone?
Thanks
Howard
Code Snippet
exec sp_executesql N'INSERT INTO "pit1_lamda".."Planalt"
("ElNo","Item","MvmtDate","NewValue","OldValue","PlanAltId","PlanNo","Timestamp","User_Id","RBNo","CreatorId","CreatorTypeCode","CreatedDate","ExitNo","PBTxnTriggerId","PremHistNo","RegContractPremium","WaiverPrem","SinglePremTot","PlanMvtId","SingMvtID","PLFAID","TrancheId")
VALUES (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12,@P13,@P14,@P15,@P16,@P17,@P18,@P19,@P20,@P21,@P22,@P23); INSERT INTO
"pit1_lamda".."Planalt"
("ElNo","Item","MvmtDate","NewValue","OldValue","PlanAltId","PlanNo","Timestamp","User_Id","RBNo","CreatorId","CreatorTypeCode","CreatedDate","ExitNo","PBTxnTriggerId","PremHistNo","RegContractPremium","WaiverPrem","SinglePremTot","PlanMvtId","SingMvtID","PLFAID","TrancheId")
VALUES (@P24,@P25,@P26,@P27,@P28,@P29,@P30,@P31,@P32,@P33,@P34,@P35,@P36,@P37,@P38,@P39,@P40,@P41,@P42,@P43,@P44,@P45,@P46)',N'
@P1 varchar(6),@P2 int,@P3 datetime,@P4 varchar(7),@P5 varchar(1),@P6 int,@P7 varchar(12),@P8 int,@P9 varchar(8),@P10 varchar(4),@P11
varchar(12),@P12 tinyint,@P13 datetime,@P14 int,@P15 int,@P16 int,@P17 money,@P18 money,@P19 money,@P20 int,@P21 int,@P22 int,@P23 int,
@P24 varchar(6),@P25 int,@P26 datetime,@P27 varchar(18),@P28 varchar(12),@P29 int,@P30 varchar(12),@P31 int,@P32 varchar(8),@P33 varchar(4),@P34
varchar(12),@P35 tinyint,@P36 datetime,@P37 int,@P38 int,@P39 int,@P40 money,@P41 money,@P42 money,@P43 int,@P44 int,@P45 int,@P46 int',
'000000',80,'01-01-2008','1463286','0',27425002,'043902305X2 ',57153,'mtstdat4','0000',
'mtstdat4 ',1,'03-05-2008',0,0,0,$0.0000,$0.0000,$0.0000,4250207,0,0,3001752,
'000000',11,'03-02-2008','10 In Force (V011)','3 AwaitIssue',27425003,'043902305X2 ',57155,'mtstdat4','0000',
'mtstdat4 ',1,'03-05-2008',0,0,0,$0.0000,$0.0000,$0.0000,4250207,0,0,3001752
Hello:
We have an old 16-bit app that runs fine in SQL 7.0 but on our test SQL 2000 box some reports generate the following error "System Message 10202 - The application fetch buffer size is less than the cursor select statement requires". Any ideas what this means, I am not much of a coder. The MS Knowledge base does not list much on this.
Thanks,