Yeah, Yeah, I know...
But I was asked, and have no idea (and hope I never have to have any experience)
I was hoping my 6.5 days were Loooooooooooong behind me....guess not
I'm working on explaining that an upgrade is a better solution....
Anyone have any war stories?
Is it possible (please say no)
I am planning to upgrade our SQL Server 2000 box from Win NT to Windows 2000. Have anyone done the same thing and has encounter problems? Thank you.
View 2 Replies View RelatedHi,I am new to Win2k and SQL server and need to back up everything each night.I used the supplied NT backup utility to schedule a backup but this missedsome files that were open or in use.I am more used to Unix/Informix where I could backup everything whether itwas in use or not.How or what would you recommend I use to do my backups?Thanks.
View 2 Replies View RelatedHiya!
I'm having a problem installing SQL Server 7 Enterprise Edition (no service pack)on a Windows 2000 Server SP 2 machine (256 MB RAM,40 GB drive) off an original MSDN CD. Only the client components get installed. This is the output from the SQLStp.log file:
15:19:51 Begin Setup
15:19:51 7.00.623
15:19:51 Mode=Normal
15:19:51 ModeType=NORMAL
15:19:51 ValueFTS returned: 1
15:19:51 ValuePID returned: 1
15:19:51 ValueLic returned: 1
15:19:51 GetDefinitionEx returned: 0, Extended: 0xf000000
15:19:51 System: Windows NT Server
15:19:51 SQL Server ProductType: Enterprise Edition [0x3]
15:19:51 Begin Action: SetupInitialize
15:19:51 End Action SetupInitialize
15:19:52 Fixed install: 0
15:19:52 Begin Action: CheckRequirements
15:19:52 Platform ID: 0xf0000000
15:19:52 Version: 5.0.2195
15:19:52 Processor Architecture: x86 (Pentium)
15:19:52 File Version - C:NTSRVRSystem32shdocvw.dll: 5.0.3315.2879
15:19:52 ComputerName: SERVER-5IQ8359Z
15:19:52 User Name: Administrator
15:19:52 IsAllAccessAllowed returned: 1
15:19:52 C:NTSRVRTEMP\_ISTMP44.DIRscm.exe -Silent 1 -Action 6 -Timeout 5000 -Service MSSQLServer
15:19:57 Process Exit Code: (0)
15:19:57 OS Language: 0x409
15:19:57 End Action CheckRequirements
15:19:57 Begin Action: Detection
15:19:57 End Action Detection
15:19:57 Begin Action: ODBCLocked
15:19:57 End Action ODBCLocked
15:19:57 This combination of Package and Operating System allows a client install only.
15:19:59 The Enterprise Edition server component cannot be installed on Windows NT Server using this CD. Only client components will be available for installation.
15:19:59 Reading SoftwareMicrosoftWindowsCurrentVersionCommonFilesD ir ...
15:19:59 CommonFilesDir=C:Program FilesCommon Files
15:19:59 Windows Directory=C:NTSRVR15:19:59 Begin Action: ShowDialogs
15:19:59 Begin Action: DialogShowSdWelcome
15:20:00 End Action DialogShowSdWelcome
15:20:00 Begin Action: DialogShowSdLicense
15:20:01 End Action DialogShowSdLicense
15:20:01 Begin Action: DialogShowSdRegisterUserEx
15:20:06 End Action DialogShowSdRegisterUserEx
15:20:06 Begin Action: DialogShowCdKey
15:20:06 End Action DialogShowCdKey
15:20:06 Begin Action: DialogShowPID
15:20:06 End Action DialogShowPID
15:20:06 Begin Action: DialogShowSdSetupType
15:20:10 [SetupTypeSQL]
15:20:10 szDir=C:MSSQL7
15:20:10 Result=303
15:20:10 szDataDir=C:MSSQL7
15:20:10 End Action DialogShowSdSetupType
15:20:10 Begin Action: DialogShowSdComponentMult
15:20:10 basesys=0, baseinst=0,basedata=0
15:20:19 SQL program folder: C:MSSQL7
15:20:19 SQL data folder: C:MSSQL7
15:20:19 Windows system folder: C:NTSRVRSystem3215:20:19 Prog req: 46703, Data req: 0, Sys req: 24971
15:20:19 Prog avail: 2147483, Data avail: 2147483, Sys avail: 2147483
15:20:19 Prog req vs. avail, 71674, 2147483
15:20:19 Data req vs. avail, 0, 2147483
15:20:19 Sys req vs. avail, 24971, 2147483
15:20:19 DisplaySystemPreReq
15:20:19 [SQLComponentMult]
15:20:19 Component=
15:20:19 Result=1
15:20:19 End Action DialogShowSdComponentMult
15:20:19 Begin Action: DialogShowSdStartCopy
15:20:38 End Action DialogShowSdStartCopy
15:20:38 Begin Action: DlgCPLLicense
15:20:38 End Action DlgCPLLicense
15:20:38 End Action ShowDialogs
15:20:38 Begin Action ProcessBeforeDataMove:
15:20:38 DeinstallStart returned (C:MSSQL7): -1
15:20:38 DeinstallStart returned (C:MSSQL7): 0
15:20:38 End Action ProcessBeforeDataMove:
15:20:38 Begin Action ProcessComponentSelection:
15:20:38 End Action ProcessComponentSelection
15:20:38 Begin Action LogSelectedComponents:
15:20:38 MgtTool
15:20:38 MgtToolSEM
15:20:38 MgtToolSEMHTML
15:20:38 MgtToolSEMMSD98
15:20:38 MgtToolSEMMSD98SYS
15:20:38 MgtToolSEMMSD98Res
15:20:38 MgtToolSEMMSD98Hlp
15:20:38 MgtToolSEMHelp
15:20:38 MgtToolSEMSEMSys
15:20:38 MgtToolSEMRes1033
15:20:38 MgtToolSEMResIntl
15:20:38 MgtToolSEMMSD98RsI
15:20:38 MgtToolProfiler
15:20:38 MgtToolProfilerHelp
15:20:38 MgtToolProfilerRes1033
15:20:38 MgtToolProfilerResIntl
15:20:38 MgtToolQryanlz
15:20:38 MgtToolQryanlzHelp
15:20:38 MgtToolQryanlzRes1033
15:20:38 MgtToolQryanlzResIntl
15:20:38 MgtToolDTCCLi
15:20:38 MgtToolWzcnflct
15:20:38 MgtToolWzcnflctWzcnsys
15:20:38 MgtToolWzcnflctWzcnHlp
15:20:38 MgtToolUtilSys
15:20:38 MgtToolUtilBinn
15:20:38 Connect
15:20:38 ConnectConnSys
15:20:38 ConnectConn9x
15:20:38 ConnectConnNT
15:20:38 Books
15:20:38 BooksBookso
15:20:38 DevTools
15:20:38 DevToolsHeaders and Libraries
15:20:38 DevToolsHeaders and LibrariesInclude
15:20:38 DevToolsHeaders and LibrariesLibx86
15:20:38 DevToolsHeaders and LibrariesLibAlpha
15:20:38 DevToolsHeaders and LibrariesESQLC
15:20:38 DevToolsMDAC SDK
15:20:38 DevToolsVDI
15:20:38 DevToolsVDIInc
15:20:38 DevToolsVDISamples
15:20:38 DevToolsDbg Int
15:20:38 DevToolsDbg IntDbg Int Common
15:20:38 DevToolsDbg IntEXE
15:20:38 Samples
15:20:38 SamplesADO
15:20:38 SamplesDBLIB
15:20:38 SamplesDTS
15:20:38 SamplesESQLC
15:20:38 SamplesMSDTC
15:20:38 SamplesODBC
15:20:38 SamplesODS
15:20:38 SamplesOLEAut
15:20:38 SamplesRepl
15:20:38 SamplesSQLDMO
15:20:38 SamplesSQLNS
15:20:38 Core
15:20:38 CoreSys
15:20:38 ODBC
15:20:38 OLEDB
15:20:38 Repostry
15:20:38 RepstSys
15:20:38 CoreMisc
15:20:38 Monarch
15:20:38 Jet
15:20:38 NetCore
15:20:38 NetExt
15:20:38 SFExt
15:20:38 ReplExt
15:20:38 Core1033
15:20:38 CoreIntl
15:20:38 CrMi1033
15:20:38 CrMiIntl
15:20:38 Monr1033
15:20:38 MonrIntl
15:20:38 SFEx1033
15:20:38 SFExIntl
15:20:38 RpEx1033
15:20:38 RpExIntl
15:20:38 SysCore
15:20:38 VOLEDB
15:20:38 VODBC
15:20:38 MiscCore
15:20:38 MCHlp
15:20:38 MC1033
15:20:38 MCIntl
15:20:38 CnctBinn
15:20:38 CrRepCom
15:20:38 {E07FDDC8-5A21-11d2-9DAD-00C04F79D434}
15:20:38 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
15:20:38 End Action LogSelectedComponents
15:20:38 Begin Action MoveFileData:
15:21:11 End Action MoveFileData
15:21:11 Begin Action ProcessAfterDataMove:
15:21:11 DeinstallSetReference (C:MSSQL7sqlservr.exe) returned: 0
15:21:11 End Action ProcessAfterDataMove
15:21:11 Begin Action InstallPkgs:
15:21:11 Setup is installing Microsoft Management Console (MMC) ...
15:21:11 D:x86Otherinstmmc.exe /Q
15:21:35 Process Exit Code: (0)
15:21:35 Setup is installing HTML Help ...
15:21:36 HTML Help installer exit code: 0
15:21:36 End Action InstallPkgs
15:21:36 Path successfully updated.
15:21:36 %SystemRoot%system32;%SystemRoot%;%SystemRoot%syst em32WBEM;C:Program FilesSymantecpcAnywhere;C:MSSQL7BINN
15:21:36 Begin Action SelfRegister
15:23:39 Return code: 0
15:23:39 End Action SelfRegister
15:23:39 Begin Action SetupRegistry:
15:23:39 End Action SetupRegistry
15:23:39 Begin Action PostSetupRegistry:
15:23:39 C:MSSQL7BINNdcomscm.exe /RegServer
15:23:39 Process Exit Code: (0)
15:23:39 C:PROGRA~1COMMON~1MICROS~1SQLDEB~1sqldbreg.exe -RegServer
15:23:39 Process Exit Code: (-2147312566) Error loading type library/DLL.
15:23:40 C:PROGRA~1COMMON~1MICROS~1DATABA~1wzcnflct.exe /RegServer
15:23:40 Process Exit Code: (0)
15:23:40 End Action PostSetupRegistry
15:23:40 Begin Action SetupFolders:
15:23:40 Microsoft SQL Server 7.0 Folder refreshed.
15:23:40 End Action SetupFolders
15:23:40 Action CleanUpInstall:
15:23:40 Uninstall command: C:NTSRVRIsUninst.exe -fC:MSSQL7Uninst.isu -c"C:MSSQL7sqlsun.dll" -msql70.mif
15:23:40 SetTracking: {E07FDDA8-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDA9-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDAA-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDAB-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDAC-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDAD-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDAF-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB0-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB1-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB2-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB3-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB4-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB5-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB6-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB7-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB8-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDB9-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDBA-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDBB-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDBB-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDBD-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDC8-5A21-11d2-9DAD-00C04F79D434}
15:23:40 SetTracking: {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
15:23:40 Installation Succeeded
Thanks,
Sarah
I have been asked to install Sql 7 on a Win2K server. I am looking for White papers, articles, postings etc which identify potential issues or known issues. I have looked through MSDN, Win2K, Microsoft Sql7 and TechNet for specifics. Any suggestions?
Thank you,
Troy
error msg in summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows 2000 Server Service Pack 4 (Build 2195)
Time : Wed Feb 14 03:31:27 2007
LDINTSQL1 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Wed Feb 14 03:39:30 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_Support.log
error msg in C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_LDINTSQL1_Core.log
Microsoft SQL Server 2005 Setup beginning at Wed Feb 14 03:31:27 2007
Process ID : 2176
\ldnas1msdn versionsServer ApplicationsSQL Server 2005 stdServerssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/1/14 3:31:27
Complete: LoadResourcesAction at: 2007/1/14 3:31:27, returned true
Running: ParseBootstrapOptionsAction at: 2007/1/14 3:31:27
Loaded DLL:\ldnas1msdn versionsServer ApplicationsSQL Server 2005 stdServersxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/1/14 3:31:27, returned true
Running: ValidateWinNTAction at: 2007/1/14 3:31:27
Complete: ValidateWinNTAction at: 2007/1/14 3:31:27, returned true
Running: ValidateMinOSAction at: 2007/1/14 3:31:27
Complete: ValidateMinOSAction at: 2007/1/14 3:31:27, returned true
Running: PerformSCCAction at: 2007/1/14 3:31:27
Complete: PerformSCCAction at: 2007/1/14 3:31:27, returned true
Running: ActivateLoggingAction at: 2007/1/14 3:31:27
Complete: ActivateLoggingAction at: 2007/1/14 3:31:27, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2176" returned false.
Running: PerformSCCAction2 at: 2007/1/14 3:31:27
Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435
Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2007/1/14 3:31:27, returned true
Running: PerformDotNetCheck at: 2007/1/14 3:31:27
Complete: PerformDotNetCheck at: 2007/1/14 3:31:27, returned true
Running: ComponentUpdateAction at: 2007/1/14 3:31:27
Complete: ComponentUpdateAction at: 2007/1/14 3:31:54, returned true
Delay load of action "DetectLocalBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchLocalBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchLocalBootstrap__2176" returned false.
Running: PerformDotNetCheck2 at: 2007/1/14 3:31:54
Complete: PerformDotNetCheck2 at: 2007/1/14 3:31:54, returned true
Running: InvokeSqlSetupDllAction at: 2007/1/14 3:31:54
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Failed to determine path to bootstrap files : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: setupsqlsetupactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:04 2005
Function Name: sqls::InvokeSqlSetupDllAction::perform
Source Line Number: 1663
any ideas?
thanks
Is anyone here successfully running SQL Server 6.5 in a Windows 2000Server??We tried to and had some runtime problems relative to tempdb.
View 3 Replies View RelatedHi
Today I have task to move all UDB's including matser,msdb form Windows 2000 server to Windows 2003 Advacned Server with 64bit(8 Hours Down time)
Present Plan
1.Install same Version of SQL Server in Destination Server
2.Take all Databases Backup
2.Move DTS,JOB and Scripts with same location
3.Stop both servers SQL Server's
4.Deattch all Databses and Move to Destination Server
5.Place all Databases(Same Loaction i.e Soruce Server master DB is C:<folders>.. Place in Destination Server C:<folder>..)
6.Start the Databse Servers(Destination)
7.Port the Apllication and Test.
Note:for our project we are using windows users,so that no problem with Orphan users.
Please some body Advice me, or suggest me
..it is ok
I want to know how people are backup up their win2k system and SQL 2000 server. If you want a run backup once a night and first backup win2k file system and then run backup using sql agent will that work?
Thanks.
Hi All Can I install sqlserver2000 as a desktop version in win2k professional ?
Please Help
Starting with Win2k you are not suppossed to have to install MDAC, as it comes with the OS. What about when I install SQL7 and it automatically installs MDAC. Do I have to reinstall MDAC in this case?
View 2 Replies View RelatedI have heard that when installing Win2K sp2 and SQL 2000 sp2 they should be done in a certain order. Does anyone know anything about this?
Thanks!
JJ
Does anyone know the 'trick' in getting sqlmail (sqlserver 7.0) to work with Outlook 2000 on a windows 2000 server machine. I've setup a mail profile on Outlook, but it is not listed in the dropdown menu in the sqlmail properties.
Outlook communicates with my smtp/pop3 mail server - no problem. I can't get sqlmail to interface with outlook. Basically it is telling me that it cannot find ANY profiles on the server.
My shop is thinking of migrating from NT4 to Win2K. Is anyone running SQL7 on Windows 2000 (which edition?)? How's you're experience been? Anyone hear any anecdotes of particular things that don't work (well)?
Thanks for your input.
does anyone know where I can get the admin pack for win2k. thanks
View 1 Replies View RelatedI am new to MSDE and want to deploy it in my company (because it is free).However, when I install it in a W2K professional machine, there is a messagebox saying that a "strong SA password is required". How can I solve theproblem?Arthur Cheung(The MSDE engine was downloaded from the microsoft sql server web page)
View 1 Replies View RelatedI only can install client-side of SQLServer2000 on Win2kProfestional
But i need to set up server-side, so can i?
Hello all,
There are have 2 nodes.Both on cluster and on a test_domain.Test domain is a active directory domain.
Node_A & node_B has C and D drives.D drive will have programs.
There is one common drive E - where data will go.
Now,I have to install SQL2000 on it.Can anyone tell me in layman's way how to install it.Do I have to have D drive in shared mode?When I give remote connection what should I give here?
Win 2000 clustered was installed by a NT expert and is working fine.
I am assuming drive_D will hold the SQl programs.
I tried one article posted here from Sqlserver preformance side but nothing worked.
Does it matter as both the nodes are on a Active Directory?
Any hint may help.
thanks!
Ok I'm am going through a rather painful experience of installing Reporting Services on:
Windows 2000 SP4
MDAC 2.8
.Net Framework 2.0
IIS 5.0
SQL Server 2005 Developer
I have installed RS 2005 on Windows 2003, and seen it installed on XP no problems. However this is a nightmare.
RS goes ahead and installs - note that there is no Network/Local service option on the service accounts just Local system or the domain account option. I have tried using the Local system and tried using the NT AUTHORITY/SYSTEM.
After the installation I go to the Reporting Services Configuration Tool, where I have crosses on:
- Server Status
- Report Server Virtual Directory
- Report Manager Virtual Directory
- Web Service Identity
- Database Setup
I- nitialization
So I go to report server/manager and click on "New.." on each to create the virtual directories and check "apply default settings" and click "Apply", all goes well
Web Service Identity I cannot change so I go to:
C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportServer
sreportserver.config
and change the web service account to:
<WebServiceAccount><<MACHINE NAME>>ASPNET</WebServiceAccount>
When I restart the reporting services service I no longer see a warning in the reporting services log file about the WebServiceAccount
I go back to the Reporting Services Config Tool, where I have crosses on the following:
Web Service Identity
Database Setup
Initialization
The Web Service Identity stays greyed out...
I go to Database Setup:
connect to the server
select the reportingserver database
leave it set as service credentials
Click "Apply"
and I get the most vague of all error messages:
"There was a failure applying your change
A virtual directory must first be created before performing this operation"
What virtual directory, where???
I look in the log files..nothing. I look in the event viewer...and...nothing.
I look on here...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=628231&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1682492&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=493194&SiteID=1
Either unanswered or there is the one answer but it is not relevant in this case.
Can someone please provide some advice before I lose my sanity?
Thanks in advance
Hi,
I recently migrated our database from Access to SQL Server 2005. All the WinXP users can connect to the new SQL2005 database. But all the Win2K machines fail to log on. To diagnose the problem, I tried to connect from a Wind2K machine using an .udl file. The connection failed because "a provider failed to initialize".
The SQL2005 server is residing on a WinXP machine. Users log on via SQL Server authentication layer using a dedicated login that only has read/write privileges to one specific database.
Does anyone know a solution? Thanks in adance.
Regards,
Vladislav
I've got SQL 2000 set up on a cluster running Windows 2000 Advanced Server (w/SP1).
Setup for Failover Clustering appeared to succeed normally on both nodes.
The SQL 2000 server logs show:
2001-01-11 10:02:57.82 server SuperSocket Info: Bind failed on TCP port 1433.
2001-01-11 10:02:57.85 server SQL server listening on Shared Memory, Named Pipes.
2001-01-11 10:02:57.85 server SQL Server is ready for client connections
I've checked to see if something else is using port 1433 (unlikely) and don't see anything.
The physical node that SQL 2000 is currently on has no other cluster resources assigned to it.
Any ideas?
Hi
While configuring an active / active cluster, do I need to run the SQL setup on both nodes?
The SQL2K setup installs binaries on localdisks of both nodes - hence the question.
thanks
Liju
My server is a dual AMD x64 2.19 GHz with 8 GB RAM running under Windows Server 2003 Enterprise Edition with service pack 1 installed. We have SQL 2000 32-bit Enterprise installed in the default instance. AWE is enabled using Dynamically configured SQL Server memory with 6215 MB minimum memory and 6656 maximum memory settings.
I have now installed, side-by-side, SQL Server 2005 Enterprise Edition in a separate named instance. Everything is running fine but I believe SQL Server2005 could run faster and need to ensure I am giving it plenty of resources. I realize AWE is not needed with SQL Server 2005 and I have seen suggestions to grant the SQL Server account the 'lock pages in memory' rights. This box only runs the SQL 2000 and SQL 2005 server databases and I would like to ensure, if possible, that each is splitting the available memory equally, at least until we can retire SQL Server 2000 next year. Any suggestions?
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi,
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Thanks.
Hi,
When I am trying to access SQL Server 2000 database from another machine i got this error
Server: MSg 17, Level 16, State 1 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
but I could access the database on same server and in that server i could access other databases in different server.
Hi All,
View 14 Replies View RelatedHi,
View 36 Replies View RelatedWhen I proposed start to use SQL Server 2005 for new VS 2005 web sites, one of my co-workers responded that
we will update the old SQL Server 2000 databases to SQL Server 2005 when we are ready to use 2005 SQL Server.
Questions:
1. Any expected problems to upgrade old 2000 databases to new 2005 SQL Server?
2. I have installed both 2005/Management Studio Express and 2000/Enterprise Manager in my PC. Any expected
problems when running both 2000 and 2005 SQL Server at the same database server?
3. What is the best configuration for running SQL Server 2005 when we have old 2000 databases? Upgade or not upgrade?
TIA,
Jeffrey
I am getteing
need help
Query analyzer error Unable to connect server local Msg17, level 16,state 1
ODBC SQL server driver [DBNETLIB]SQL server does not exist
Hi,
I am having a problem connecting my .net applications from the application server to the database server. When I run the application from my windows xp (sp2) box it works fine. When I try to connect via SQL Management Studio to the database server from the application server I get the same error.
Here is the error:
System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Here is the Environment:
App Server:
Windows Server 2003 Standard Edition
Inside Company's Firewall/ Network
Database Server:
Windows Server 2000 Advanced Edition
SQL Server 2000 SP4
Remote Connections to the Server is checked
Enable Protocols: Named Pipes & TCP/IP
TCP/IP Port: 1402 (I don't know why it isn't the default of 1433)
The db server is sitting out side the Company's firewall (don't ask me why). I can access it fine from inside the firewall on my XP box but not from windows server 2003. There is a web server outside the our network that also connects to the db server with no problem and that is running Windows Server 2003 Web Edition.
I can ping the db server from the app server using the IP address.
I tried using the IP address and the port 1402 in my connection string but that didn't work from any machine (XP and Server).
I imagine the issue is somehow related to the company's firewall but why would it only block Windows Server 2003 and not XP?
What do I tell the network admin to change?
Any help would be appreciated.
Thanks,
Oran
if you can restore a database to Server B using Server A as the service. Meaning we would issue the command on Server A but somehow point to Server B as where we want the restore to happen.
The backup file would be in a location independent of both servers.
Dear all,On Win2000 server with SP3, I am trying to access a SQL Server 7.0database, "TestDB", from VB6 via a SQL Server ODBC system DSN using ADO2.7. In SQL Server Enterprise Manager, there is a login named "Tester".In its property window, NO "Server Roles" was assigned but its"Database Access" was set to "TestDB". This login was also made as theuser of "TestDB" with "public", "db_datareader" and "db_datawriter"selected as its "Database role membership". All the tables I am tryingto access in "TestDB" were created under "Tester".My code is like:Set conn = New ADODB.Connectionconn.Open "DSN=TestDSN;UID=Tester;PWD=test"Set cmd = New ADODB.Commandcmd.ActiveConnection = conncmd.CommandText = SQLset rs = cmd.Execute()If I set the SQL to something like "SELECT * FROM tbl_test", I alwaysget an error of "-2147217865" saying "[Microsoft][ODBC SQL ServerDriver][SQL Server] Invalid object name tbl_test". If I set the SQL to"SELECT * FROM Tester.tbl_test", everything runs properly. Could anyoneplease kindly advise why the first SQL is not working? Or in otherwords, why must I prefix the table name with its owner while the DBconnection is already made under that owner name? Thanks in advance.Tracy
View 10 Replies View Related