InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 05:55:44 GMT20http://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]GilaMonster (3/8/2013)[/b][hr]Because you're not continually (as in many times a minute) creating and dropping tables in a user database. At least I hope you're not.[/quote]:-) LOL..right..Thanks,PedroFri, 08 Mar 2013 03:18:09 GMTPiManéhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]PiMané (3/7/2013)[/b][hr]If the number of files for tempdb is related with the number of CORES why doesn't the rule apply for database files?[/quote]Because you're not continually (as in many times a minute) creating and dropping tables in a user database. At least I hope you're not.Fri, 08 Mar 2013 02:51:58 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspxSo having a FILEGROUP to store the indexes and another for the data isn't an advantage?It just useful for "organizing" the database?But FILEGROUP for different types of data is useful as long as the indexes are in the same FILEGROUP then?If the number of files for tempdb is related with the number of CORES why doesn't the rule apply for database files?Is it because tempdb has "load" coming from "all directions" (all databases, DMVs, ...), hence having more IO?Thanks,PedroThu, 07 Mar 2013 15:14:25 GMTPiManéhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]PiMané (3/7/2013)[/b][hr][quote][b]GilaMonster (3/7/2013)[/b][hr]Really? Have you tried that?[/quote]Not with indexes... just some more "sensible" data (accounts, orders, ...) and "fixed" data (like countries, regions, currencies, ...).[/quote]You might want to try that 'don't back up the indexes' idea before you implement that in production. Don't want an unpleasant surprise...Thu, 07 Mar 2013 11:09:45 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]GilaMonster (3/7/2013)[/b][hr]Really? Have you tried that?[/quote]Not with indexes... just some more "sensible" data (accounts, orders, ...) and "fixed" data (like countries, regions, currencies, ...).Thu, 07 Mar 2013 10:34:44 GMTPiManéhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]PiMané (3/7/2013)[/b][hr]If there are IO issues should the new ndf file be on the same RAID or a different, probably new one (since the IO is on the RAID adding the new file to the existing RAID won't make a difference.. or will it?!)?[/quote]If a drive is under IO load then splitting a database file into two and leaving the second on the same drive results in exactly the same IO load to the disk.[quote]I can create an INDEX FILEGROUP to store the index and not make a backup on the index data and if I need to restore the database I'll just recreate the indexes since I have the DDL.[/quote]Really? Have you tried that?Thu, 07 Mar 2013 10:21:01 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspx[quote][b]GilaMonster (3/7/2013)[/b][hr]The one file/ x cores is for TempDB, not for user databases. Unless you have reason to split a user database for recoverability or IO issues, you probably don't want to split it.[/quote]Thanks,If there are IO issues should the new ndf file be on the same RAID or a different, probably new one (since the IO is on the RAID adding the new file to the existing RAID won't make a difference.. or will it?!)?And are my thoughts on FILEGROUPS correct? They are useful to "split" data for backup/restore issues?I can create an INDEX FILEGROUP to store the index and not make a backup on the index data and if I need to restore the database I'll just recreate the indexes since I have the DDL.Thanks,PedroThu, 07 Mar 2013 09:59:06 GMTPiManéhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspxThe one file/ x cores is for TempDB, not for user databases. Unless you have reason to split a user database for recoverability or IO issues, you probably don't want to split it.Thu, 07 Mar 2013 09:46:52 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspxHi! In your case, to the users databases i'll try to start with just one data file and try to start and maintain just one file for the transaction log, for the system database tempdb, you could use 4 database files and one file for the transaction log :)Bye!Thu, 07 Mar 2013 09:36:58 GMTandrecesarrhttp://www.sqlservercentral.com/Forums/Topic1427883-1550-1.aspxHi,In an 8 CORE machine with 3 RAID10 (data files, log files and tempdb) what's the appropriate number of files or filegroups for a database with lots of users and IO? I saw a SQLPass presentation where it said 1 file for 4 CORES..If a database has 2 files and since the files are on the same RAID set is it worth creating also 2 FILEGROUPS (one for each data file) or the porpoise of FILEGROUPS is to put "sensible" data on one and not so sensible data on another so the 1st one has backups more frequently?Thanks,PedroThu, 07 Mar 2013 03:49:35 GMTPiMané