I have just completed a default install of MS SQL Server 2005 x64 edition on a 1 processor Quad core, 8GB, Windows Server 2003 Standard x64 R2 machine in an Active Directory Domain. It has 2 arrays configured with 2) 36Gb drives mirrored for the OS as C: and 3) 147Gb drives in a RAID5 array as E: drive.
I am simply the server guy who was asked to install SQL server for some projects in the future. The company will be bring in people to to the dev.
I wanted to setup the server as best as I can and so I've been searching around for "best practices" for fresh installs.
Anyone have any suggestions on things to configure/setup to improve the performance of the default install?
In addition, I want to redirect the databases to the E: drive and separate them from the OS drive (C:). Does anyone have any information on doing this? I have searched and found a few articles, but thought I would ask first.
It is probably noticeable that I have limited SQL configuration skills.
Thanks,
A simple IT guy trying to build a system right
I am working as a consultant on a project to upgrade an Access 2000 db to SQL Server. My client has bought off on everything, and they're ordering a new dedicated box this week. They're getting a rackmount machine running Windows Server and SQL Server 2005.
My expectation was that their IT people would take care of administrative & security issues such as setting the machine up, installing & starting SQL Server and configuring the proper accounts. Suprisingly though, they're going to mount the machine in the rack, turn it on and let me do all of this.
I'm new at SQL Server, but I'm comfortable working with database objects (tables, views, etc...) I'm not so comfortable with the networking or administrative side of things. It took me a couple of hours to be able to connect to the DB on my desktop machine over my home network. You can see why I'm intimidated at the prospect of getting things integrated & running on a pretty large corporate network.
Maybe I'm overblowing this, but this just gives me the willies.
Are my fears justified? Am I going to be ok if I just follow the standard procedures for allowing TCP/IP connections to the server? Am I going to have to deal with firewalls? (I think I know the answer - "it depends on their network.." - that's what I'm scared of.. I don't know anything about their network, and I don't know enough about networking in general to figure things out..)
Are there any other best practices that I should follow for a fresh install?
hello, what is the general consensus on installing SQL 2005. I usually run a backup of SQL 2000 dbs and then restore on SQL 2005 and change compatibility to 9.0. Is it the right way to upgrade? I'm only asking because I also did one db in-place to SQL 2005 and thought it went well until I browsed my system dbs. All of them are missing tables that usually appear in SQL 2005 system dbs. Other than that I haven't run into too many problems.
I was playing around with SQL2k5 Express, but decided to download Enterprise using my MSDN subscription. I installed it, but none of the services are running. I don't understand why?
I've checked the requirments and I notice that Vista x64 is not on the list for compatible OS's.
I do get this when trying to install:
- SQL Server Edition Operating System Compatibility (Warning)
Messages
SQL Server Edition Operating System Compatibility
Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
Also, during the install, Componoents to Install: All the services are greyed out... is that because they can't be installed or because they're going to be installed by default?
Anyone else have it running on Vista Ultimate x64? Am I doing something wrong or does it just not install on this version of Vista?
Is it possible for SQL 2005 Express SP2 to ignore the UPGRADE parameter during a commandline install? We would like to use one commandline to handle both a fresh intstall and an upgrade depending on which is needed.
Does it make any difference which order the commandline parameters are used?
Do I need to write something to check if an upgrade or fresh install is needed and then feed the appropriate parameters?
New ssrs istall. I think they loaded sp2. It's a cluster, but ssrs was not clustered (I think)
When I attempt to open report manager, i just get
SQL Server Reporting Services Home
with no option for creating a folder etc, like i have on development
When I attempt to deploy to ther server I get :
Deploying to http://amsqlclusterxx/reportserver/ Error rsItemAlreadyExists : The item '/Retailer' already exists.
How do I create an ssrs reports folder?
Also, and this is strange, but in vs.net I had to create a new shared datasource after removing the old one on the report with the same name. The report renders fine when I do an f5 pointing to a new datasource, but I no longer have the RUN "!" icon available while in the data tag to run my query. Why is this?
In general, with the introduction of schemas in 2005, is it considered "bad practice" to tell people to create new tables in the "dbo" schema?
Our product documentation contains a "quick start" guide for users who just want to get the product up and runing. We suggest that the customer creates a database for our application. This database is configured with a user that is assigned to the 'db_owner' role (we want to keep things as simple as possible) that we use to connect to the database. This database will only be used by our application. In this situtation is it okay to use the "dbo" schema, or should we consider creating another schmea for all our tables?
Are the any "best practices" for using schemas in SQL 2005?
I am re-posting this from the security Forum where it remains un-answered.
OK, Here's the set up.
I have a Windows 2003 box, soon to have SSL installed
On it is IIS 6.0, SQL 2005 Standard Edition (5Cal user lic)
SOON I'll have a prod enviornemnt where a web app being served by IIS is accessing SQL. I can go into SQL and set up a user account, call it MyAppSQLAcess, and code that into the connectionn string and lock it down to the tables/db it has access to. Or I can do it w/windows authentication, or I can do it a number of other ways, the question is this:
What is the best way for an asp.net app being server by IIS 6.0 to access data from SQL 2005 server when they are all on the same BOX? WRT Speed and security?
Does anybody have a link to either of these two documents. My company is getting ready to go through an audit and we need some firepower and to know what is expected. Any help with obtaining microsoft SQL Server 2005 best practices documents is appreciated.
Greetings I have a scenario where a table's after insert & after update triggers write to a history table. On this particular table, the history rows are quite small, so the occassional deadlock condition is inevitable.
In SQL Server 2000, I taught the application guys to handle these kinds of exceptions themselves, sleep a second, and retry. In 2005 (and I assume 2008) we now have TRY CATCH in T/SQL.
What are the pro's and con's of catching deadlocks in your T/SQL code (triggers or sprocs) .vs. the "old way" of catching it at the application level? I'm sure this has been discussed before, but search returns a lot of unrelated postings...
I'm thinking it's better to catch this at the application level, under the assumption that it's better to make the client(s) do the work than the database, but I'm sure there are considerations I'm not taking into account here. What experiences do you folks have to share on this?
Does anyone have any advice or useful experience configuring memory management for SQL Server 2000 and 2005 instances residing on the same box? I'm looking for advice on whether I should just completely leave it up to SQL Server and Windows to allocate memory or should I attempt to put ceilings on certain instances.
We have a live OLTP database for which we create full backups every week and differential backups every day. Recently we added an OLAP database, which we need to update daily with changes from the live database.
This is the process we are planning to use. 1. Restore last full OLTP backup. 2. Apply the last differential OLTP backup. At this point we should have a replica of the live OLTP database. 3. Update OLAP database based on the OLTP replica database. 4. Delete the OLTP replica database.
Two questions. 1. If different from the process above, how is this OLTP-to-OLAP transformation typically done in the industry? 2. What is the best way to implement this process with SQL Server 2005?
I would like to know best practices for setting up my environment. To date, I've had everything running on a single server. That would include the database engine, SSIS, SSAS and SSRS. The box configuration is dual hyperthreaded 3.6GHz Xenon with 4GB of RAM on Windows Server 2003. I just received a much larger server and want to configure it to maximize our environment. The new box contains four 2.6GHz Quad Core processors with 16GB of RAM. I would like to know if I should split the ETL and database engine from SSAS and SSRS, or should this box have enough horse power to house it all and use my other box as a dev environment. Also, we are planning to purchase Performance Point 2007 primarily for PAS and Scorecard Manager so please take that into consideration as well. Any comments are greatly appreciated.
Microsoft recommends using Windows authentication instead of SQL Server authentication in SQL Server 2005 for improved security. What are the Microsoft best practices for implementing this? Will be helpful if someone also provides some links that talks about this....
I am currently running Windows XP Professional Service Pack2. It already has MSDE & SQL Server 2000 installed (although I just uninstalled MSDE in the vain hope that it might present the installer with a more straightforward upgrade).
I have tried installing with the default instance & a new instance (I don't really care - I just need to install the darn thing). I just want the basic database & Books On-line, nothing fancy.
Here is the Summary log, for what it's worth:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Feb 06 16:45:14 2007
Machine : ANTHONYY1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : MSXML 6.0 Parser (KB927977) Product Version : 6.00.3890.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BOL_1.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : MSXML 6.0 Parser (KB927977) Product Version : 6.00.3890.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ANTHONYY1 Product : SQLXML4 Error : Setup is preparing to continue with the installation. --------------------------------------------------------------------------------
Here is the SQLSetup0011_ANTHONYY1_Core(Local).log
Microsoft SQL Server 2005 Setup beginning at Tue Feb 06 16:45:14 2007 Process ID : 2560 C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/1/6 16:45:14 Complete: LoadResourcesAction at: 2007/1/6 16:45:14, returned true Running: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14, returned true Running: ValidateWinNTAction at: 2007/1/6 16:45:14 Complete: ValidateWinNTAction at: 2007/1/6 16:45:14, returned true Running: ValidateMinOSAction at: 2007/1/6 16:45:14 Complete: ValidateMinOSAction at: 2007/1/6 16:45:14, returned true Running: PerformSCCAction at: 2007/1/6 16:45:14 Complete: PerformSCCAction at: 2007/1/6 16:45:14, returned true Running: ActivateLoggingAction at: 2007/1/6 16:45:14 Complete: ActivateLoggingAction at: 2007/1/6 16:45:14, returned true Running: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14 Complete: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2560" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2007/1/6 16:45:14 Complete: PerformDotNetCheck2 at: 2007/1/6 16:45:14, returned true Running: InvokeSqlSetupDllAction at: 2007/1/6 16:45:14 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [ANTHONYY1] Trying to find Product Code from command line or passed transform If possible, determine install id and type Trying to find Instance Name from command line. No Instance Name provided on the command line If possible, determine action Machine = ANTHONYY1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = ANTHONYY1, Article = XMLDomDocument, Result = 0 (0x0) Machine = ANTHONYY1, Article = Processor, Result = 0 (0x0) Machine = ANTHONYY1, Article = PhysicalMemory, Result = 0 (0x0) Machine = ANTHONYY1, Article = DiskFreeSpace, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSVersion, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSServicePack, Result = 0 (0x0) Machine = ANTHONYY1, Article = OSType, Result = 0 (0x0) Machine = ANTHONYY1, Article = iisDep, Result = 0 (0x0) Machine = ANTHONYY1, Article = AdminShare, Result = 0 (0x0) Machine = ANTHONYY1, Article = PendingReboot, Result = 70011 (0x1117b) Machine = ANTHONYY1, Article = PerfMon, Result = 0 (0x0) Machine = ANTHONYY1, Article = IEVersion, Result = 0 (0x0) Machine = ANTHONYY1, Article = DriveWriteAccess, Result = 0 (0x0) Machine = ANTHONYY1, Article = COMPlus, Result = 0 (0x0) Machine = ANTHONYY1, Article = ASPNETVersionRegistration, Result = 0 (0x0) Machine = ANTHONYY1, Article = MDAC25Version, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: ANTHONYY1 ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: CheckPassed Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0'> <Func Name='DisplaySCCWizard'> CSetupBootstrapWizard returned 1 <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'> Failed to find help file for LCID :2057 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2007/1/6 16:49:35, returned true Running: SetPackageInstallStateAction at: 2007/1/6 16:49:35 Complete: SetPackageInstallStateAction at: 2007/1/6 16:49:36, returned true Running: DeterminePackageTransformsAction at: 2007/1/6 16:49:36 Complete: DeterminePackageTransformsAction at: 2007/1/6 16:49:47, returned true Running: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47 Complete: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47, returned true Running: OpenPipeAction at: 2007/1/6 16:49:47 Complete: OpenPipeAction at: 2007/1/6 16:49:47, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2007/1/6 16:49:47 Complete: CreatePipeAction at: 2007/1/6 16:49:47, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false. Running: PopulateMutatorDbAction at: 2007/1/6 16:49:47 Complete: PopulateMutatorDbAction at: 2007/1/6 16:49:47, returned true Running: GenerateRequestsAction at: 2007/1/6 16:49:47 SQL_Engine = 3 SQL_Data_Files = 3 SQL_Replication = 3 SQL_FullText = 3 SQL_SharedTools = 3 SQL_BC_DEP = 3 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = 3 Connectivity = 3 SQL_Tools90 = 3 SQL_WarehouseDevWorkbench = 3 SDK = 3 SQLXML = 3 Tools_Legacy = 3 TOOLS_BC_DEP = 3 SQL_Documentation = 3 SQL_BooksOnline = 3 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2007/1/6 16:49:48, returned true Running: CreateProgressWindowAction at: 2007/1/6 16:49:48 Complete: CreateProgressWindowAction at: 2007/1/6 16:49:48, returned true Running: ScheduleActionAction at: 2007/1/6 16:49:48 Complete: ScheduleActionAction at: 2007/1/6 16:49:48, returned true Skipped: InstallASAction.11 Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: No install request found for package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: No install request found for package: "ns", install will be skipped as a result. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result. Running: InstallSqlAction.11 at: 2007/1/6 16:49:48 Installing: sqlsupport on target: ANTHONYY1 Complete: InstallSqlAction.11 at: 2007/1/6 16:49:51, returned true Running: InstallSqlAction.12 at: 2007/1/6 16:49:51 Installing: sqlncli on target: ANTHONYY1 Complete: InstallSqlAction.12 at: 2007/1/6 16:49:55, returned true Running: InstallSqlAction.18 at: 2007/1/6 16:49:55 Installing: owc11 on target: ANTHONYY1 Complete: InstallSqlAction.18 at: 2007/1/6 16:49:56, returned true Running: InstallSqlAction.21 at: 2007/1/6 16:49:56 Installing: sqlwriter on target: ANTHONYY1 Complete: InstallSqlAction.21 at: 2007/1/6 16:49:58, returned true Running: InstallSqlAction.22 at: 2007/1/6 16:49:58 Installing: bcRedist on target: ANTHONYY1 Complete: InstallSqlAction.22 at: 2007/1/6 16:50:0, returned true Running: InstallSqlAction.9 at: 2007/1/6 16:50:0 Installing: msxml6 on target: ANTHONYY1 Complete: InstallSqlAction.9 at: 2007/1/6 16:50:2, returned true Running: InstallToolsAction.11 at: 2007/1/6 16:50:2 Installing: sqlsupport on target: ANTHONYY1 Complete: InstallToolsAction.11 at: 2007/1/6 16:50:5, returned true Running: InstallToolsAction.12 at: 2007/1/6 16:50:5 Installing: sqlncli on target: ANTHONYY1 Complete: InstallToolsAction.12 at: 2007/1/6 16:50:8, returned true Skipped: InstallToolsAction.13 Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis: No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result. Running: InstallToolsAction.18 at: 2007/1/6 16:50:8 Installing: owc11 on target: ANTHONYY1 Complete: InstallToolsAction.18 at: 2007/1/6 16:50:10, returned true Running: InstallToolsAction.20 at: 2007/1/6 16:50:10 Installing: BOL on target: ANTHONYY1 Complete: InstallToolsAction.20 at: 2007/1/6 16:52:2, returned true Running: InstallToolsAction.22 at: 2007/1/6 16:52:2 Installing: bcRedist on target: ANTHONYY1 Complete: InstallToolsAction.22 at: 2007/1/6 16:52:4, returned true Running: InstallToolsAction.9 at: 2007/1/6 16:52:4 Installing: msxml6 on target: ANTHONYY1 Complete: InstallToolsAction.9 at: 2007/1/6 16:52:6, returned true Skipped: InstallNSAction.10 Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result. Running: InstallSqlAction at: 2007/1/6 16:52:7 Installing: sql on target: ANTHONYY1 Error: MsiOpenDatabase failed with 110 Failed to install package This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. Error: MsiOpenDatabase failed with 110 for MSI D:ServersSetupSqlRun_SQL.msi Setting package return code to: 1620 Complete: InstallSqlAction at: 2007/1/6 16:52:27, returned false Error: Action "InstallSqlAction" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Running: InstallToolsAction.10 at: 2007/1/6 16:52:27 Installing: sqlxml4 on target: ANTHONYY1 Error Code: 0x8007006e (110) Windows Error Text: The system cannot open the device or file specified.
Source File Name: sqlchainingminorbuildactionbehavior.cpp Compiler Timestamp: Mon Jun 13 14:30:04 2005 Function Name: sqls::MinorBuildActionBehavior::modifyRequest Source Line Number: 65
Complete: InstallToolsAction.10 at: 2007/1/6 16:55:59, returned false Error: Action "InstallToolsAction.10" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Action "InstallToolsAction" will return false due to the following preconditions: Condition "Action: InstallToolsAction.10 has finished and failed." returned true. Installation of package: "tools" failed due to a precondition. Step "InstallToolsAction" was not able to run. Skipped: InstallASAction Skipped: Action "InstallASAction" was not run. Information reported during analysis: No install request found for package: "as", install will be skipped as a result. Skipped: InstallRSAction Skipped: Action "InstallRSAction" was not run. Information reported during analysis: No install request found for package: "rs", install will be skipped as a result. Skipped: RepairForBackwardsCompatRedistAction Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis: Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run: Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchMSDE2000" failed due to a precondition. Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run: Action: "UninstallForSQLAction" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchLibertySql" failed due to a precondition. Skipped: UninstallForRS2000Action Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis: Action: "UninstallForRS2000Action" will be skipped due to the following condition: Condition "Action: InstallRSAction was skipped." returned true. Running: ReportChainingResults at: 2007/1/6 16:55:59 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 1620 Error Code: 0x80070654 (1620) Windows Error Text: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Sep 1 22:23:05 2005 Function Name: sqls::ReportChainingResults::perform Source Line Number: 3097
---- Context ----------------------------------------------- sqls::HostSetupPackageInstallerSynch::postCommit sqls::HighlyAvailablePackage::preInstall led due to cancel code received from cancel source: 29539
...and here is the SQLSetup0011_ANTHONYY1_SQL.log:
=== Verbose logging started: 06/02/2007 16:52:14 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe === MSI (c) (00:54) [16:52:14:284]: Resetting cached policy values MSI (c) (00:54) [16:52:14:284]: Machine policy value 'Debug' is 0 MSI (c) (00:54) [16:52:14:284]: ******* RunEngine: ******* Product: D:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (c) (00:54) [16:52:14:284]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (00:54) [16:52:14:284]: Grabbed execution mutex. MSI (c) (00:54) [16:52:14:299]: Cloaking enabled. MSI (c) (00:54) [16:52:14:299]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (00:54) [16:52:14:299]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (A4:98) [16:52:14:299]: Grabbed execution mutex. MSI (s) (A4:00) [16:52:14:299]: Resetting cached policy values MSI (s) (A4:00) [16:52:14:299]: Machine policy value 'Debug' is 0 MSI (s) (A4:00) [16:52:14:299]: ******* RunEngine: ******* Product: D:ServersSetupSqlRun_SQL.msi ******* Action: ******* CommandLine: ********** MSI (s) (A4:00) [16:52:21:080]: Note: 1: 2203 2: D:ServersSetupSqlRun_SQL.msi 3: -2147024873 MSI (s) (A4:00) [16:52:21:080]: MainEngineThread is returning 1620 MSI (c) (00:54) [16:52:21:080]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (00:54) [16:52:21:080]: MainEngineThread is returning 1620 === Verbose logging stopped: 06/02/2007 16:52:21 ===
I suppose an error dialog (or log message) that actually told you what is wrong and then what to do is too much to ask for. (Or an installer than just copied all the files into place). :(
Log Location: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log MSP Error: 29537 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.
I tried to search internet, however, I couldn't get solution.
My SQL server 2005 is standard version, OS Windows server 2003 sp2, I am using Administrator account to install it.
I never installed previous beta versions on my computer before. But now I have some serious problem after an incomplete de-install and a re-install of SQL server 2005 express advanced. I hope anybody can help me to solve this. Because the first installation eas not succesfull I had to do an de-install. I have tried to unstall through start/control panel/ add-remove programms and even there not all programs were removed. And that caused the problem. After that I wanted to re-install again but an msi file was missing. So I did a de-install agian. Tried to re-install again but with a lot of errors. After looking at the library I found a program: Windows Install CleanUp. I installed it and that even gives an error for all programs installed with SQL 2005. After that I ran a program called MsiInv to clean but without any succes because this program reported a run-tim error. I have all reports on my computer but don't know how to attach them. If you think you can help me I could send you all the reports. Regards,
I'm trying to Service Pack 4 a fresh installation of SQL 2000 (a named instance called 'SQLSERVER2000') and get the error "Installation of the Microsoft Full-Text Search Engine package failed. (-2147467259) 0x80004005 Unspecified Error" towards the end of the process thus I cannot service Pack my fresh installation of SQL 2000. I have done this many times before on other machines, but its not working for me this time.
At http://www.dbforums.com/ ( http://www.dbforums.com/showthread.php?t=1198047 ) someone ran into this problem and mentioned to re-install Microsoft Full-Text Search. I have followed the article http://support.microsoft.com/kb/827449 but run into problems at step 2C. At step 2C it says to start the Microsoft Search service via the Services console, but Microsoft Search was nowhere to be found.
Going back a step to Step 2B it says that all registry keys that were previously-deleted are now available and the previously-deleted 'MSSearch' folder is recreated. I took a look, but both the keys and folder WERE NOT there.
It is a fresh OS installation of MS Windows 2003 Standard SP1, 768MB RAM and is running fine.
Can you please point me in the right direction here?
Hi everyone I have been trying hard to unserstand the way my isp does things sort of a communication gap I guess. The problem is I want to use the personal website... yes I know this is a SQL forum and that is what I am going to get at. I having a problems with the database aspect of the whole situtation, I can't creat a aspnetdb.mdf on their server because that name aready exists and I am assuming that it is the system and not a user that ows it. Also I can't name the other database personal.mdf either for the same reasons, so someone at the isp has had me creat a different name database during the install process of the application and that worked fine for a little while and now it does not work no more and I am getting old faster than I'd like. So here is my plan my plan is to wipe out the current database for the application on my workstation but first make a list of tables and then create a new database for that web application. So I ask is it feasible and what do I have to look out for and if it is not to much to ask what steps might take to accomplish such a task. I want to thank anybody that is willing to help me in this matter. DKB
Can anybody provide me with the guidelines to install a fresh copy of SQL Server 2000 Enterprise Edition? The previous installation included a system account and it was on the same drive as the operating system. I remember reading this was not a good practice. Am I wrong? thanks in advance
greets, im coding a few queries to a table. im storing sets of records into the table, each set of records will haev a different batch id. so basically 2 sets of records can occupy this table at the same time, and their batch id is the main key (with 2 other fields also being PKs). i want to compare the 2 sets in the same table and get the differences: 1. records that were added 2. records that were updated 3. records that were deleted
ive written queries for the added records, and the updated records but i cant get the query for finding deleted records. the logic looks good to me but im obviously missing something so i could use a fresh pair of eyes. here is the table def:
Code:
CREATE TABLE [dbo].[UPCXREF_BATCH] ( [BATCH_ID] [char] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [CHAIN_CODE] [char] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [UPC] [char] (16) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL , [ITM_CODE] [char] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , [ITM_CATEGORY] [char] (2) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , [CREATE_DATE] [datetime] NULL ) ON [PRIMARY] GO
ALTER TABLE [dbo].[UPCXREF_BATCH] WITH NOCHECK ADD CONSTRAINT [PK_UPCXREF_BATCH] PRIMARY KEY CLUSTERED ( [BATCH_ID], [CHAIN_CODE], [UPC] ) ON [PRIMARY] GO
and here are the queries ive gotten so far
Code:
/* This section retrieves all UPDATED records */ SELECT 'U' as FLAG, b2.CHAIN_CODE as CHAIN_CODE, b2.UPC, b2.ITM_CODE, b2.ITM_CATEGORY FROM UPCXREF_BATCH b2 INNER JOIN UPCXREF_BATCH b1 ON b2.CHAIN_CODE=b1.CHAIN_CODE AND b2.UPC=b1.UPC AND (b2.ITM_CODE<>b1.ITM_CODE OR b2.ITM_CATEGORY <> b1.ITM_CATEGORY ) WHERE b2.BATCH_ID='BTC0002' AND b1.BATCH_ID='BTC0001'
/* This section retrieves all NEW records */
SELECT 'A' as FLAG, CHAIN_CODE, UPC, ITM_CODE, ITM_CATEGORY FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0002' AND (CHAIN_CODE NOT IN (SELECT CHAIN_CODE FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0001') OR UPC NOT IN (SELECT UPC FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0001'))
here was my attempt to get deleted records which looks like it makes sense but isnt working
Code:
SELECT 'D' as FLAG, CHAIN_CODE, UPC, ITM_CODE, ITM_CATEGORY FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0001' AND CHAIN_CODE NOT IN (SELECT CHAIN_CODE FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0002') AND UPC NOT IN (SELECT UPC FROM UPCXREF_BATCH WHERE BATCH_ID='BTC0002')
here batch 'BTC0001' is the older set of records that already existed and batch 'BTC0002' is the new set we just inserted into the table. am i missing something else?
I have done DTS that export data from SQL to .xls, it works perfect, my problem is my table from SQL get truncated everytime before i load data but my .xls file always come with previous records which I don't want. i.e. if my Sql table had 3 rows , when i finish to execute the dts, my .xls come with 3 rows, when I exec again, my table get truncated and my .xls add another 3 rows. How can I solve this
It’s coming along but there are some problems, ASP.NET actually has 2 posts not 1. And the java totals are correct but it should be Java, 3, 10 (all in one line) Category.....Topics...Posts ASP.NET.........2........1 C#................1........1 Java..............1........1 Java..............1........2 Java..............1........7
Overview: use category id to get count of topics then use the topic id to get the count of posts.
SELECT C.CategoryName, T.ThreadCount AS Threads, T.PostCount AS Posts FROM Category AS C LEFT OUTER JOIN (SELECT tt.CategoryID, PostID.PostCount, COUNT(tt.ThreadName) AS ThreadCount FROM Thread AS tt LEFT OUTER JOIN (SELECT ThreadID, COUNT(PostID) AS PostCount FROM Post AS P GROUP BY ThreadID) AS PostID ON tt.ThreadID = PostID.ThreadID GROUP BY tt.CategoryID, PostID.PostCount) AS T ON C.CategoryID = T.CategoryID WHERE (C.CategoryID = T.CategoryID) GROUP BY C.CategoryName, T.ThreadCount, T.PostCount ORDER BY C.CategoryName
Re: Best Practices (security): Should SQL Server (2005) *not* be installed on the same physical HD as the Windows OS (Server 2003 R2) ?
Hi,
We're setting up some new servers, and today I'm looking into best practices for the SQL Server Setup portion of it.
The servers have include 2 x 250G HD, and from what I've read, where IIS is concerned, it should not be installed on the drive that has the OS on it, for security reasons. I was wondering if the installation of SQL Server should be on the non-OS drive as well ?
I am doing performance tuning of SP/Query in Dev-Test environment.
I found that SQL Server caches plan between successive executions.
So if I test/execute SP 10 times, after 1st or 2nd execution, SQL server will pull-up plan-info from CACHE...Not from SQL SERVER Or Database...
Means i am not getting correct answer...
I found this 2 commands:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
But they say that executing above command might interfere/bother other people executing other query/sp on this server.
They also say that: Freeing the plan cache causes, for example, a stored procedure to be recompiled instead of reused from the cache. This can cause a sudden, temporary decrease in query performance.
Part of query was using Dynamic-SQL executed with EXEC command.
I replaced that with SP_EXECUTESQL.
How can I start testing of each SP-run with Fresh/Blank CACHE ?
I went to one of the Microsoft "Ready To Launch" events over a year ago. Microsoft was gracious and gave everyone who attended a free copy of Visual Studio 2005 and SQL Server 2005. I have installed the Visual Studio and use it all of the time. I also installed the SQL server 2005 but I can not find the application on my computer. After the install the only items that appear to have been installed are the following: SQL Server Configuration tools(SQL Server Configuration manager,SQL Server Error and usage reporting, SQL Server surface area confiuration, Reporting Services configuration). There is also a menu icon labeled "Microsoft SQL server upgrade advisor" and SQL server upgraded wizard. That is all. I can't find anything that is analogus to the Enterprise manager that was in SQL server 2000 or anything that is analogous to Query Analyzer of 2005.
Can someone help me out? We use SQL server 2005 so I know how it looks. I just can't see where it insalled. I don't think it did?
I have never installed sql server before and I didnt know if I just take the sql server 2005 standard edition media and boot off it and do a fresh install that way or do I have to install Windows server
The program shortcut "Visual Studio 2005 Command Prompt" seems to be mising from the "Visual Studio 2005 Command Prompt" Start menu added by the current Microsoft SQL Server 2005 Express Edition Toolkit. Where is it? How to workaround?
I am trying to do Download details SQL Server 2005 Samples and Sample Databases (April 2006) -> GettingStartedWithSQLSamples.htm which says "a. Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt." but I can find no such command prompt within "Visual Studio Tools", only "Visual Studio 2005 Remote Debugger{, Configuration Wizard}".
What's wrong? How to fix or workaround? I'd install .NET SDK 2.0 to get it's Command Prompt but that's about 570MB merely for a command prompt!
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID
********************************************************************************** Product Installation Status Product : Express Database Services (SQLEXPRESS) Product Version (Previous): 1399 Product Version (Final) : Status : Failure Log File : D:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXE SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools Error Number : 1332 Error Description : *** Shared String ID 1332 Not Found *** ----------------------------------------------------------------------------------
********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 1332
