July 24, 2006 at 4:13 pm
Comments posted to this topic are about the content posted at http://qa.sqlservercentral.com/columnists/awarren/sqlserver2005adventures.asp
August 10, 2006 at 9:26 am
For training?
Would it not be easier to setup a Virtual PC (or equivalent) and simply discard any changes after each training session? That would take about 5 seconds instead of 45 mins, saving you loads of time!
😉
But maybe I misunderstood the whole thing or there is some other reasons you need "real" machines?
August 10, 2006 at 12:26 pm
We do have and use VPC in some cases, especially multi server scenarios. In fact, I can build VPC images quickly using the RIS server and a specially floppy driver that allows the VPC session to boot to the network. Our reasoning for a real machine install was a combination of wanting to keep it simple for students where we could (believe or not, not everyone has used VPC or equivalent) and to gather some real world experience. In truth we could also add SQL to the image and save time that way. That's not to say that you're not right, it's possible that over time we'll move to virtual images exclusively.
August 11, 2006 at 5:56 am
start /wait "F:\ENGLISH\SQL2005\DEVELOPER\SQL Server x86\Servers\setup.exe" /settings "C:\Documents and Settings\Administrator\Desktop\SQLInstall.INI" /qn
when i run the batch in a cmd window "/settings" is an invalid sqitch comes up.
F is the DVD drive.
Any help greatly appreciated.
August 11, 2006 at 7:41 am
If you omit the /Settings and all past that, does the first part work ok? Verified that the path you have for the ini is correct?
August 11, 2006 at 8:41 am
August 11, 2006 at 8:43 am
August 14, 2006 at 4:52 am
August 14, 2006 at 7:24 am
Not exactly an obvious problem!
August 10, 2007 at 7:32 am
I think Microsoft ADS would ahve been your best bet for this. Using ADS you could have deployed completely configured machines, with all OS SP's and SQL installed remotely, in one swoop, without leaving your desk.
September 17, 2008 at 4:40 pm
There is a list of features here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\Setup\FeatureList
It doesn't seem to match all of them 1:1
I also used setup LOGNAME=C:\setup\setup.cab
I extracted the cab and looked at the files inside.
the SQLSETUP000x_ _Core(Local).log file has detailed setup logging
Look for a section like this:
Running: GenerateRequestsAction at: 2008/8/17 12:34:9
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = -1
SQL_FullText = -1
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 = -1
SDK = -1
SQLXML = -1
Tools_Legacy = -1
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
3 is installed on local disk I believe, and -1 is not installed. These seem to match up almost exactly with the FeatureList registry key for all values 3. I would guess it might also match up for any values <> -1. I guess 1/2 are install on first use, install from network, or unused.
I bet the items that are 3's above are required dependencies for the other installed Features.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply