Sql Installations

Apr 14, 2008

Dear All,
how many types of installations are there in sql server?

Vinod
Even you learn 1%, Learn it with 100% confidence.

View 4 Replies


ADVERTISEMENT

Multiple Msde Installations

Jan 17, 2007

Hi All
I am new to this forum.
I want to know if MSDE can be installed twice (two instances) on a single computer?
I will be thankful for details provided by you.
Radhesham

View 4 Replies View Related

Conlidate Databases For Multiple Installations

Nov 6, 2006

1. install a SQL Express instance such as myexpress;

2. create some databases with tables such as db1 and db2;

3. Reinstall SQL Express with the same instance name "myexpress". I assume we need reinstall SQL Express myexpress again becuase of bad operations.

4. Open the myexpress by management tool but I can not see db1 and db2 databases but the datafiles and logfiles are in the data directory.

The question is what I need to do so I can consolidate exited databases so they can be seen in "myexpress" instance by management tool?

View 1 Replies View Related

Confused About MSSQL Express Installations

May 21, 2006

I have this confusion because as I am trying to install "SQL Server Management Studio Express", the installers said I already have it.

Q1. Do I need it if I already have SQL Server Management Studio for Server 2005?

Q2.

How many ways to have SQL Express installed on your PC?

- Seperate downloads

- Visual Studio 2005 Retail

- SQL Server 2005

In that regards, will all methods are basically install the same set of components into the machine?

Q3. I don't find any relevant item in the "Add or Remove Programs" regarding to SQL Express.

Is that because SQLExpress is just an database instance not a application item?

Q4. Where are the files of Express in the file system?

I saw in c:Program filesMicrosoft SQL Server, a few directories like

80, 90, MSSQL.1, MSSQL.2, MSSQL.3, MSSQL.3, MSSQL.4

Which one of those belongs to SQL Express and which belongs to SQL Server 2005?

Is the directory structure identical with other types of installation (standalone and VS IDE)?



Thanks

Stanley











View 3 Replies View Related

SQL Server 2005 SP1 Installations Issues.

Dec 1, 2006

Hi all.

Any assistance regarding this would be greatly appreciated.

I am trying to intall SP1 on SQL Server 2005 and am experiencing some difficulties with regards to Authentiction modes.

I have tried to use Windows Authetication for All instances and it states that the account information could not be verified for one or more services. I only have one instance which is the default and have Database Services and Reporting services listed in the Products text box. I have also tried using SQL Server Authentication using the password of a SQL Server account but am still experiencing problems.

Any ideas or suggestions would be greatly appreciated.

Thanks in advance.

View 1 Replies View Related

How To Cosolidate Databases Of SQL Express From Multiple Installations?

Nov 6, 2006

1. install a SQL Express instance such as myexpress;

2. create some databases with tables such as db1 and db2;

3. Reinstall SQL Express with the same instance name "myexpress". I assume we need reinstall SQL Express myexpress again becuase of bad operations.

4. Open the myexpress by management tool but I can not see db1 and db2 databases but the datafiles and logfiles are in the data directory.

The question is what I need to do so I can consolidate exited databases so they can be seen in "myexpress" instance by management tool?

View 1 Replies View Related

Visual Studio And SQL Server Express Installations

Sep 19, 2007



They say that the definition of insanity is doing the same thing again and again while expecting a different outcome.
I must be going insane.

To top it off, the first time I tried to enter this message the post failed.

I installed visual studio 2005 and SQL express in the spring and began working with them. Life was good. I got distracted for several months and when I went back in I saw the 2008 beta 2 versions of VS and VWD. I uninstalled everything and installed the new versions, but kept having problems with missing links in the help files. I am a newbie, so the help files were important to me so I decided to go back to the old versions.

I deleted everything again, used the MSI cleanup utility to make sure everything was deleted and tried to reinstall the 2005 versions. At one point I got SQL server installed, but had to use a different (besides SQLexpress) instance name and was unable to link it with VWD. I have repeatedly uninstalled and reinstalled (maybe a dozen times) while trying various means of deleting file contents and under the programs/apdata and Microsoft SQL directories and in various sequences to no avail. The latest message is below along with the end of the log file.

Does anyone know a good hosting vendor for the visual studio authoring environment? (just half kidding)

Thanks for any help ... bill

Error message ....

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlShutDownRANUInstance%40sqls%3a%3aService%3a%3aStart%40x3



Log file summary .....


Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Tue Sep 18 14:29:26 2007

HOMEWXP : The current system does not meet minimum hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.
HOMEWXP : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : HOMEWXP
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : MSXML 6.0 Parser (KB933579)
Product Version : 6.10.1200.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : MSXML 6.0 Parser (KB933579)
Product Version : 6.10.1200.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (3) The system cannot find the path specified.
Error Number : 29503
--------------------------------------------------------------------------------
Machine : HOMEWXP
Product : Microsoft SQL Server Management Studio Express
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SSMSEE_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.

Time : Tue Sep 18 16:11:03 2007

List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_MSXML6_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SQL.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SSMSEE_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_HOMEWXP_WI.log


SQL Log

Property(S): SqlFullTextDefaultPath = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
Property(S): FTERefPath.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
Property(S): QuotedServiceGroupFTS.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = HOMEWXPSQLServer2005MSFTEUser$HOMEWXP$SQLEXPRESS
Property(S): FTEInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLEXPRESS
Property(S): FTERudeInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.1
Property(S): FTERegRoot.68C6D15C_77E0_11D5_8528_00C04F68155C = SOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1MSSearch
Property(S): FTEInstanceSubDir.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.1MSSQL
Property(S): FTEStartupTypeBeforeInstall = 3
Property(S): FTEStatusBeforeInstall = 6
Property(S): FTEStartupType = 3
Property(S): FTEStatus = 6
Property(S): InstanceRegKey.7827AB3E_7041_406A_9591_4DB66042927F = Microsoft SQL ServerMSSQL.1
Property(S): InstanceName.7827AB3E_7041_406A_9591_4DB66042927F = SQLEXPRESS
Property(S): SqlVerComFT.BB43EC2E_1D73_400F_AE2F_F370407BC222 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.BB43EC2E_1D73_400F_AE2F_F370407BC222 = c:Program FilesMicrosoft SQL Server90
Property(S): FTESqlInstanceBin.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): FTESqlInstance.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): FTESqlInstanceBinRef.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef
Property(S): FTESqlInstanceDotNumber.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1
Property(S): SqlVer.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL Server90
Property(S): FTESharedCompRoot.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL Server90
Property(S): Sql.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL Server
Property(S): ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program Files
Property(S): CAFTERemovePerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C = $SQLEXPRESS
Property(S): CAFTEUninstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef|c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
Property(S): CAFTEUpgradeFTERefFiles.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLServer$SQLEXPRESS:c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef
Property(S): CAFTEUpgradeFTERefFilesRollBack.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef
Property(S): CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef|c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
Property(S): CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLEXPRESS
Property(S): CARemoveFTEServiceDependency.68C6D15C_77E0_11D5_8528_00C04F68155C = msftesql$SQLEXPRESS
Property(S): CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D318-77E0-11D5-8528-00C04F68155C}:NT AUTHORITYNetworkService
Property(S): FTERegInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLEXPRESS
Property(S): FTERegRudeInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.1
Property(S): FTEUPGRADE.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): FTEUpgrade30.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): FTEUpgradeMSSearchApp.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLServer$SQLEXPRESS
Property(S): FTEUpgradeMSSearchStandalone.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): CostingComplete = 1
Property(S): FTEInstID.68C6D15C_77E0_11D5_8528_00C04F68155C = 1
Property(S): FTEAppID.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D318-77E0-11D5-8528-00C04F68155C}
Property(S): FTEAdminCLSID.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D37C-77E0-11D5-8528-00C04F68155C}
Property(S): FTEIFTEAdmin.68C6D15C_77E0_11D5_8528_00C04F68155C = {64f6bd6f-cc0d-11d6-9a15-505054503030}
Property(S): FTEMSFTEPXY.68C6D15C_77E0_11D5_8528_00C04F68155C = {64f6bdd4-cc0d-11d6-9a15-505054503030}
Property(S): FTEDollarInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = $SQLEXPRESS
Property(S): FTEServiceName.68C6D15C_77E0_11D5_8528_00C04F68155C = msftesql$SQLEXPRESS
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = c:ae2ebb64c8a0ed8236221093549918Setup
Property(S): SourcedirProduct = {B0F9497C-52B4-4686-8E73-74D866BBDF59}
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {278C8A54-0676-4D3F-B85A-BFF2EF53C1CF}
Property(S): ProductToBeRegistered = 1
MSI (s) (44:68) [14:51:03:640]: Note: 1: 1708
MSI (s) (44:68) [14:51:03:640]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (44:68) [14:51:03:671]: Cleaning up uninstalled install packages, if any exist
MSI (s) (44:68) [14:51:03:671]: MainEngineThread is returning 1603
MSI (s) (44:58) [14:51:03:671]: Destroying RemoteAPI object.
MSI (s) (44:A0) [14:51:03:671]: Custom Action Manager thread ending.
=== Logging stopped: 9/18/2007 14:51:03 ===
MSI (c) (2C:00) [14:51:06:593]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:00) [14:51:06:609]: MainEngineThread is returning 1603
=== Verbose logging stopped: 9/18/2007 14:51:06 ===

View 2 Replies View Related

Failed SQL 2005 SP1 Installations (Hotifx.exe Crashes)

Nov 7, 2007

i just don't kown was happening... please help!....

thanks!
11/06/2007 21:44:25.532 ================================================================================
11/06/2007 21:44:25.548 Hotfix package launched
11/06/2007 21:46:07.532 Attempting to install instance: SQL Server Native Client
11/06/2007 21:46:07.532 Attempting to install target: BTS-108
11/06/2007 21:46:07.548 Attempting to install file: sqlncli.msi
11/06/2007 21:46:07.673 Attempting to install file: \BTS-108c$4afc0bb080422f7b54a29ff48HotFixSqlncliFilessqlncli.msi
11/06/2007 21:46:07.688 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log
11/06/2007 21:46:07.719 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
11/06/2007 21:46:07.735 Failed to read registry key: Debug
11/06/2007 21:46:07.938 MSP returned 0: The installed software already has a higher version update applied.
Product version detected is 9.00.3042.00 while the update version is: 9.00.2047.00.
11/06/2007 21:46:07.954 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
11/06/2007 21:46:07.969 Failed to read registry key: Debug
11/06/2007 21:46:07.985 Successfully installed file: \BTS-108c$4afc0bb080422f7b54a29ff48HotFixSqlncliFilessqlncli.msi
11/06/2007 21:46:08.001 Successfully installed target: BTS-108
11/06/2007 21:46:08.016 Successfully installed instance: SQL Server Native Client
11/06/2007 21:46:08.048
11/06/2007 21:46:08.048 Product Status Summary:
11/06/2007 21:46:08.079 Product: SQL Server Native Client
11/06/2007 21:46:08.094 SQL Server Native Client (RTM ) - Success
11/06/2007 21:46:08.110
11/06/2007 21:46:08.126 Product: Setup Support Files
11/06/2007 21:46:08.141 Setup Support Files (RTM ) - Not Applied
11/06/2007 21:46:08.157
11/06/2007 21:46:08.173 Product: Database Services
11/06/2007 21:46:08.188 Database Services (RTM 1406 ENU) - Not Applied
11/06/2007 21:46:08.204 Reporting Services (RTM 1406 ENU) - Not Applied
11/06/2007 21:46:08.219
11/06/2007 21:46:08.235 Product: Database Services
11/06/2007 21:46:08.266 Database Services (SP2 3042 ENU) - NA
11/06/2007 21:46:08.282 Details: This update requires service pack 0,1. The service pack for product instance SQLEXPRESS is 2. Download the update for service pack 2.
11/06/2007 21:46:08.313
11/06/2007 21:46:08.329 Product: Notification Services
11/06/2007 21:46:08.344 Notification Services (RTM 1406 ENU) - Not Applied
11/06/2007 21:46:08.376
11/06/2007 21:46:08.391 Product: Integration Services
11/06/2007 21:46:08.438 Integration Services (RTM 1399 ENU) - Not Applied
11/06/2007 21:46:08.469
11/06/2007 21:46:08.485 Product: Client Components
11/06/2007 21:46:08.501 Client Components (RTM 1406 ENU) - Not Applied
11/06/2007 21:46:08.516
11/06/2007 21:46:08.532 Product: MSXML 6.0 Parser
11/06/2007 21:46:08.563 MSXML 6.0 Parser (RTM ) - Not Applied
11/06/2007 21:46:08.579
11/06/2007 21:46:08.610 Product: SQLXML4
11/06/2007 21:46:08.626 SQLXML4 (RTM ) - Not Applied
11/06/2007 21:46:08.641
11/06/2007 21:46:08.657 Product: Backward Compatibility
11/06/2007 21:46:08.688 Backward Compatibility (RTM ) - Not Applied
11/06/2007 21:46:08.704
11/06/2007 21:46:08.735 Product: Microsoft SQL Server VSS Writer
11/06/2007 21:46:08.751 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
11/06/2007 21:46:08.766

View 4 Replies View Related

What Are The High Level Considerations For 24x7 Installations?

Feb 13, 2008

in a prior "legacy" life we couldn't imagine 24x7 implementations because it was important to 1) reorganize databases periodically to remove fragmentation that adversely affected performance and 2) back up databases just in case.

In a 24x7 SQL Server 2005 implementation, high level only, how are these and other maintenance related things accomplished with confidence?

I dont think SQL cleanses its own page splits unsolicited. Are DBAs totally reliant on logs in full recovery installations where db must be up 24x7? What if the devices those logs sit on fail? What if the logs become too large? Is it likely that if you want 24x7 you're looking at Enterrise Edition only?

I'm totally aware of and confident in the sliding window partitioning thing but it seems to me there must be more out there in terms of periodic, more frequent maintenance activity.

View 3 Replies View Related

Failed SQL 2005 SP1 Installations (Hotifx.exe Crashes)

Apr 21, 2006

I am seeing repeated failures installing SP1 database services with crashes in hotfix.exe being reported and the following appearing in log files:

Property(S): SqlUpgradeMessage = SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
Property(S): UpgradeInstruction = Connect to SQL instance ZENO as sysadmin
Launch SQL statement USE master
Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql
Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallDbEngine_hotfix_install.sql
Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
epl_hotfix_install.sql
Stop service MSSQLSERVER
MSI (s) (38:80) [09:35:35:246]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log.

This is happening on a Windows 2003 SP1 system.

Any ideas?

View 19 Replies View Related

SQL Server 2008 :: Comparing Two Multi Instance R2 Installations

Apr 26, 2015

I have 2 SQL server installs for 2008 R2 configured as multi instances. I have a product called Esri ArcMap 10.3 that can be used to generate a database. When I run the wizard against one installation, the wizard successfully creates the database. When I then run the same against the other installation it fails with the following error [Microsoft][SQL Server Native Client 10.0]Invalid cursor state

I've attempted to look at the configuration of each using
select *
from master.sys.configurations

From this I found several differences

Successful Mulit instance
Optimize for Ad hoc Workloads – False
Max Degree of Parallelism - 0

UnSuccessful Multi instance
Optimize for Ad hoc Workloads – True
Max Degree of Parallelism - 4

I attempted to co-ordinate the differences running the wizard for each iteration but it always failed with the same error above. The error always seems to occur when a particular store procedure is run. There are quite a number of scripts run prior to this and are technically under the covers and only discovered via tracing, in this case using SQL Profiler. I don't have access to individual scripts that I can run incrementally to replicate the issue. I have to rely only on the Esri Wizard.

Reviewing the error against several forums suggests that this is an ODBC error but the trace I ran using SQL Profiler finds that the driver used is Native.

My question then is "What are the conditions that would cause this error above (Invalid Cursor)?" "Is there other configuration settings that are not captured via the SQL identified above?" "Could this be caused by mapped drives for data, Logs and Temp?"

View 2 Replies View Related

Re-Installation Problem (prev Installations Not Removed Completely)

Jul 14, 2006



I have installed SQL server 2005 on Win SERVER 2003, then uninstalled and then re-installed but I have found out that the previous instances are still listed and the the previous collation too (I have changed reg setting and and language option re-installation).

It looks like that removing program does not remove completely every object, probably registry values

Do you know how to perform a good uninstallation removing everything (add/remove program does not work properly as written before) ?

Any help will be very appreciated.



Thank



View 2 Replies View Related

SQLSCAN Utility Reports SQL2000 SP4 Installations As Vulnerable

May 17, 2007

Hi-



We are attempting to run the SQLScan utility from the SQL Server 2000 security tools (http://www.microsoft.com/downloads/details.aspx?familyid=9552D43B-04EB-4AF9-9E24-6CDE4D933600&displaylang=en). I have identified 6 systems with a vulnerable installation. Each developer has updated to SP4 and when I run the scan again, I can see that the instance is now at SP4 revision but it still reports that the instance is vulnerable. From all the documentation I have read, SP4 should include all previous patches. Is the SQLSCAN tool not compatible with SP4 and if so, how can I centrally determine whether I have vulnerable version on the network or not?



Is there such a tool for SQL Server 7 as SQLSCAN is for 2000?



I should state also that I am not technically proficient with SQL Server but have been tasked to scan the network for vulnerable versions that we may have and am finding SQL Server to be very confusing indeed.



View 1 Replies View Related

Can Co-installations Of MS SQL 2005 Express And Oracle 10g XE Database Server Interfere With MS SQL?

Feb 24, 2007

Hi -

I may not sound desparate, but I really am. I have spent many days now trying to install and re-install Microsoft SQL 2005 Express. I still cannot connect to the database! I have read this forum and tried various suggestions, like setting the remote connections and TCP/IP + Named Pipes. Still doesnt work!

The environment is Dell Dimension 24000 (I86) with WinXPPro.

Out of desparation, I downloaded and installed Oracle 10g XE. It works just fine !

My question is: Does the Oracle database server interfere with connecting to the Microsoft SQL 2005 Express server ?

Also, I notice that there are an awful lot of questions posted on this Forum concerning just getting your software up and running. Are there that many stupid folks out there like myself, or has this application been released prematurely ?

View 3 Replies View Related

Setup And Upgrade :: Server Installations Use The Same Domain Service Accounts?

May 21, 2015

My company doesn't allow using Local Service / Network Service accounts for SQL Server. So I created domain service accounts. Can multiple SQL Server installations use the same domain service accounts ?

View 4 Replies View Related

Side By Side Installations Of SQL2005 Express And Developer Editions

Apr 28, 2007

I have downloaded and installed VS C# Express Orcas beta 1. It appears that Express editons ov VS can only connect to SQL2005 Express and not to a high end edition which I have on my computer. In one of the Orcas forums, it was suggested that I can install SQL2005 Express side by side my high end SQL 2005. To play it safe, I wanted to get a confirmation from this forum before I do that. Is a side-by-side installation ok? thanks.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved