The 4 GB database size limit applies only to data files and not to log (LDF)
files. However, there are no limits to the number of databases
that can be loaded/created to the SQL server instance.
Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files ... You'll not be using most of the system databases intensively so you don't need to seperate them, I mean locating them on different physical disks. ... If it's being used intensively in your environment then you should locate it's log and data files on different physical disks. ... For this question you must understand the reason why we should seperate data and log files.... Of course these drives must be physically seperated so that you'll gain performance benefits. ... (microsoft.public.sqlserver.setup)
Re: PRIMARY filegroup is full - no its not! ... sp_helpdb should report the increased size immediately after the ALTER. ... > auto-shrinking, BUT auto shrink is not turned on. ... > large file size after I expand the file using "ALTER DATABASE DataLoad... > data files by subtracting the reserved space reported by sp_spaceused ... (microsoft.public.sqlserver.server)
RE: SQL 2005 Ent SP3 migration ... change to place database file on any location (SAN, DAS, any location ... DD - SQL server 2005 ... Place different file group on different MDF, and NDF data files.... The destination disk sizes are already set and I can not change them. ... (microsoft.public.sqlserver.clustering)
Re: Sql Server 2005 - system database locations ... Then drill down to Database... Note that all the data and log files get dumped to a pre-defined ... the logs somewhere different from the data files,... suggests master can be moved using ALTER DATABASE, ... (microsoft.public.sqlserver)
Re: database size ... I like the idea of multiple data files for ... Right now the database has 1 data and 1 log ... Would multiple data... But you could still have the uploaded files in ... (microsoft.public.sqlserver.server)
