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 ???
I`m planning on installing sql7 beta on my desktop. Currently I have sql6.5 client tools installed on my desktop for performing DBA tasks against our test and prod. sql6.5 servers. Does anyone know if installing sql7 will conflict with my sql6.5 client tools or cause any other problems?
Hi: After I am install SQL7.0 clent tools in my WINDOWS95, The SQL7.0 database can access very well, but I am access SQL6.5 database object(tables) then the select data is bad, why ? help me please.
I am having the following error when running the SQL upgrade wizard trying to upgrade SQL 6.5 to SQL 2000. Does anyone here know what is the problem ?
Version Switch has aborted because you do not have "Full Control" permission to one of the HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ* registry keys. Please use regedit32.exe to correct this problem and try again.
I have already checked the registry and I do have full control permission on HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ*. Please help.
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?
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 ?
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?
The database devices was showing a negative number size, so i expanded the database which has cleared this problem, however, now when users try to input a form(each form is allocated a unique reference number) for this database the reference number has reset and is starting off at 1 instead of following on from the previous form number before this problem occurred.
How can I copy a SQL 7 database from one server to another? Please tell me all the ways because I've tried the obvious and it doesn't work. (backup and restore - won't go from one server to another, DTS transfer object Wizard - does a whole pile of errors and doesn't do stored proceedures and trigures). Thanks for help in advance. Also, what is the email address to post to the listserv and where is the FAQ for SQL7? Most of my listserv's tell you where to post right at the bottom of the digest I get - any chance you guys would do that with this list? Thanks again.
Does the upgrade wizard in 7.0 help me upgrade ALL the database objects in SQL 6.5 (including stored procedures, triggers) to 7.0? Has anyone encountered any problems?
I am attempting to connect to my SQL 6.5 Server through IPX. We currently have a WindowsNT network setup with a Novell Server v3.12 running as a file and login server. When I setup IPX/SPX as a network protocal to use, and then set it in the client configuration , I get a specific error.
"Cannot Connect To SQL Server : Login Failed"
Maybe I am missing a step in my setup somewhere. Has anyone encountered this with using IPX? It connects perfectly using named pipes, but only see this error when I try to use IPX. All help is appreciated. Thank You.
I just started as a junior dba and I'm monitoring a SQL6.5 database and I need some help with a certain issue, as to what I should be looking for. Recently, the program we use to retrieve data from the database has been freezing up on everyone. What I did was just kill some user's processes from Enterprise Manager which seems to work. But we never had this problem before. And since everyone has been closing their programs prematurely, the error log contains many errors like this: Error: 1608, Severity: 21, State: 2 A network error was encountered while sending data to the front end. Error: 17824, Severity: 10, State: 0 Unable to write to ListenOn Connection pipesqlquery.....
We have a dedicated server for this database and there's about 20 requests to the database at any given time.
If anybody can tell me what to do, I would greatly appreciate it. Thank you.
Does anyone know of any issues that need to be considered when installing NT sp4. Since doing so we are getting unexpected database behaviour thanks in advance
I receive the following error message every time I run this script:
INSERT INTO archive_temp (mrn, folder, name) SELECT a.mrn, a.encounter, a.name FROM his..active a, cabinet..cabinet c WHERE imnet like 'images3%' ORDER BY a.mrn, a.encounter GO
After 10 minutes I get this ERROR MESSG: Can't allocate space for object '-1443' in database 'tempdb' b/c the 'system' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise use 'Alter database" or sp_extendsegment to increase the size of segment.
So far, i've updated the tempdb log segment from 100 mb to 500 mb shared with data. I don't understand why I am still getting this error. When I look at Performance Monitor, the log for tempdb is not peaked at all!
I need to transfer databases from one server to the other. (They are identical sort order/char set/...) but as I did all passwords were set to NULL....How can I use the generated scripts to transfer without losing them ? (Have about 300 users...) Thank you for your help !!
I just have one short question. Is there a way to change the sort order in SQL 6.5 short of re-installing the whole database? If there is, how do I go about it?
In SQL 6.5, you could Transfer (through a menu item in Enterprise Mgr) all or parts of a database to another server. It was the perfect 'copy' mechanism. What happened to it?
Is it possible to add jobs into the SQL schedule by means of a SQL script. We have 1000 remote servers to update and don't really want to do it manually.
I have heard that there are potential problems if you put service pack for NT on your server, in that it conflicts with SQL 6.5. Does anyone know of any such problems with either running 6.5 under these conditions or installing 6.5 if the service pack is already on the server. Thanks