Hi,
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 missed
some files that were open or in use.
I am more used to Unix/Informix where I could backup everything whether it
was in use or not.
How or what would you recommend I use to do my backups?
Thanks.
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.
Hiya! 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.
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?
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.
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
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
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?
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)?
I 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)
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?
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
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.
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?
SQL Server 2008 r2 - 6 GB memory...I attempted a backup on a 500GB database but it was taking way too long. I checked the resources on the box and saw the CPU at 100%. I checked the SQL Server activity log and saw a hung query (user was not even logged on) that had multiple threads so I killed it and now the CPU utilization is back to normal.
Trouble is, now all of the threads in the activity monitor for the backup show 'suspended' and the backup appears to be not doing anything.
Data got deleted on Friday evening, need to have database restored to FRiday afternoon and also some data has been entered on Monday, which needs to be there.
Windows 2003 backup utility uses the shadow copy option that allows it to copy open files. Therefore, can I use this utility to backup the .mdf and .ldf files for my SQL 2000 database? I can then attach the .mdf files if I need to restore the database to another server. Can anyone tell me if this is safe? I've tried it and it worked but I'm worried there maybe some lurking danger in using this approach.
I've written a custom script to delete backup files from location. But unable to modify now to count the number of files are deleted. How to modify the script...
/* Script to delete older than N days backup from a specific directory */
USE [db_admin] GO IF OBJECT_ID('usp_DeleteBackup', 'P') IS NOT NULL DROP PROC usp_DeleteBackup GO
SQL 7.0 SP1. We do SQL Server backup and also third part backup (with SQL agent active) of SQL Server databases. Sometimes happen this situation:
01.00 SQL Server backup of DB1 01.00 third part backup of DB1 02.00 SQL Server T-LOG backup of DB1 03.00 SQL Server T-LOG backup of DB1 03.30 SQL Server differnatial DB backup of DB1 04.00 SQL Server T-LOG backup of DB1
or this situation:
01.00 SQL Server backup of DB1 02.00 SQL Server T-LOG backup of DB1 03.00 SQL Server T-LOG backup of DB1 03.10 third part backup of DB1 03.30 SQL Server differnatial DB backup of DB1 04.00 SQL Server T-LOG backup of DB1
My questions now are: Are my SQL Server backups valid (DB,Differenatial and T-LOG)? In case of a restore operation, can I use my SQL Server backups without problem? In other words, can we leave the third part backup tool active or it should be taken away?
Can anybody clarify this for me? Thank you in advance. Franco
I'm getting this message on my third automated backup of the transaction logs of the day. Both databases are in full recovery mode, both successfully backed up at 01.00. The transaction logs backed up perfectly happily at 01:30 and 05:30, but failed at 09:30.
The only difference between 05:30 and 09:30's backups is that the log files were shrunk at 08:15 (the databases in question are the ones that sit under ILM2007, and keeping the log files small keeps the system running better).
Is it possible that shrinking the log files causes the database to think that there hasn't been a full database backup?
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.
I've recently started working with a public sector organisation who have 4 clustered sql instances that has 80% of it's db mirrored.
Looking at the transaction log - it seems that a transaction log backup is a good idea as the log is 4x larger than the data file.But I'm not allowed access to the physical server to check onto which drive I can create the trn. No RDP, no vmware - let's be honest I'm not even allowed to launch cmd line Also the Server Manager informs me "We will need to carefully look at database backups if you guys want to start doing these backups on box, as that will break our off box backup routine (it will screw the transaction chain)."
I don't understand how backing up the transaction log could break the "transaction chain"?
I currently have a SQL Server cluster setup with a Primary DB Server SERVER1 and the Standby server SERVER2. SERVER1 has been failing more than normal is the past few weeks and its takes upto 5 mins for SERVER2 realize that SERVER1 is down. I am looking for a better way to implement a backup server on production with minimum downtime. Please adivse..
Hi Friends,I have installed SQL server 2005 Express Edition and SQL Server managementI have a SQL server 2000 db backup file. I try create a new database in my SQL server 2005 express Edition and try restore that backup file from device, it only searching for file with *.bak and *.tm extension! I tried generate backup file with .bak extension and tried restore into SQl server 2005 express edition but still it is not allowing to do so! I also tried copy my database's data file and log file and paste it under SQL server 2005 express edition Data folder and still not able to read the tables.Is that any ways to do restoring for this SQL server 2000 backup file into SQL server 2005 express edition! Anybody can help me on this please...:eek:
Any help would be greatly appreciated.My problem is that I need to set up a backup SQL Server 2000 machinewhich can be used in case of a failure to my primary. All databases(30 as of now) must be an up to the minute exact copy of productionand include most recent changes in data as well as any structurechanges (Tables, Views, SP's, Triggers, Users . . etc).When I tried this using Transactional Replication, the replicationprocess gets fouled up once I introduce any kind of structure changesto the DB. I've considered the idea of doing periodic backups andrestoring it to my backup SQL server, but this does not give me theconcurrency needed with 0 latency.I've seen articles that recommend using Transaction Replication with'Scheduled Table Refresh', and also doing database dumps to restore onthe backup machine, but I have not been able to find any documentationregarding this to try out. How can I implement this type of backupstrategy in SQL 2000?