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.
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.
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 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 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 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?
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?
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
hi I want to ask the method to calculate the memory in the configuration in SQL6.5. If I have 256MB memory installed in the server, how many memory needed in the configuration of SQL6.5.
Has any every had a problem with the probe login / SQL Perfmon processes not clearing out and maxing out users connections? Microsoft has recommended I rename the sqlctr60.dll to sqlctr60.old. This causes my application event log to fill up after about 10 min because it is trying to make a connection. They say this is a problem running on a compaq server. I am running NT 4.0 sp 4, SQL6.5 sp5a. Any ideas?
I'm thinking to upgrade SQL6.5 DB to SQL 2000 but do not know all client access with SQL 6.5 utility will work ??? (The application is a vendor canned package using SQL 7.0 DB but client can access with 6.5 ---Not using ODBC) Any experts can help ? Thank you in advance !!
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.
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 was wondering if the only way to import MSaccess files into sql6.5 is to dump the MSaccess file into a text file and then recreate the structure in SQL6.5 and then use the bcp command to copy the data into the new structure.
Had to rebuild SQL server and restored SMS databases ok. But the following msgs have appeared - any clues. All help appreciated.
99/08/16 16:38:30.75 ods Error : 17824, Severity: 10, State: 0 99/08/16 16:38:30.75 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname ''. 99/08/16 16:38:30.75 ods OS Error : 232, The pipe is being closed. 99/08/16 16:38:30.77 spid16 Error : 1608, Severity: 21, State: 2 99/08/16 16:38:30.77 spid16 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information.
I designed the AlwaysOn wrong, but every time we fail over from primary server to another server, my applications cannot connect because the sql logins cannot connect to their default databases. Once I run the command to link the login with the user in the default database then the users are able to connect. Did I do something wrong when designing AlwaysOn?
