| Author |
Topic |
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
 Posted - 2007-02-28 : 15:37:19
|
| There appears to be no way to prevent SQL 2005 from installing roughly 1.5GB of stuff on the C: drive - even if you click that advanced button and select a different drive for all the components.I can't find an easy way around this, other than rebuild the C: drive on a bunch of systems. Anyone have any other ideas?-ec |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-02-28 : 16:05:37
|
| I've been having to ask the Server guys to expand the C drive of the SQL Servers on VMs as a result of this. They thought I was going bonkers at one point as they kept telling me not to install stuff on the C drive. I told them I'm not, it's the SQL Server installer doing it! For the SQL Servers on VMs, it seems we need 10GB total size for the C drive.Tara Kizer |
 |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2007-02-28 : 16:46:05
|
| I'm looking at a full test install right now with very little data, here are the folders90: 659MB (includes the samples, Books Online, SSMS, SSIS, Notification Services)MSSQL.1 (Database Engine): 96MB files, 311MB DataMSSQL.2 (Analysis Services): 32MB, No dataMSSQL.3 (Reporting Services): 66MBSo that's just over 1GB including 311MB of data (only 72MB of that is system databases). So including system databases only it's well under 1GB and that includes optional things like Analysis Services and Reporting Services.It is quite a lot but nowhere near the 1.5GB that you're seeing? |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-02-28 : 16:47:51
|
some of that is the CLR, but only about 150mb. windows won't allow you to choose where the CLR is installed IIRC. it's always C:\windows\microsoft.net\frameworkwhat the rest of it is, who knows. maybe SSMS junk? are you installing the client tools?
www.elsasoft.org |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-02-28 : 16:48:52
|
| snSQL, you're only looking at the SQL Server specific directory. The installation places files in other locations.Tara Kizer |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-02-28 : 17:15:47
|
| I'll try to post some screenshots of the install. |
|
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2007-02-28 : 17:21:43
|
| True, there will be another 150MB or so for BIDS (Visual Studio IDE). You can add about 50MB for the SQL Server CLR assemblies, but I don't think you can include the 125MB or so for installing .NET 2.0 Framework as that truly isn't part of SQL Server.So add 200MB to my first post. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-02-28 : 17:25:47
|
here are screenshots of the install.  Clicking on the 'Disk Cost' button, shows the space that will be used. -ec |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-02-28 : 17:33:03
|
quote:
Originally posted by jezeminewhat the rest of it is, who knows. maybe SSMS junk? are you installing the client tools?
deselecting the client tools and the docs reduces the footprint on C: drive to 230MB. It just doesn't make any sense though, since the E: drive had been selected for all components. I still maintain that the installer sucks.-ec |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-02-28 : 17:58:14
|
well, you don't really need the client tools on the server do you?  EDIT: I agree the installer sucks!
www.elsasoft.org |
|
|
|
|
holy crap, SQL 2005 installer completely sucks