Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 18,954 of 19,505    |
|    Bob Barrows to rja.carnegie@gmail.com    |
|    Re: Inadvertently moving table to a new     |
|    05 Nov 13 15:56:24    |
      From: reb01501@NOyahooSPAM.com              rja.carnegie@gmail.com wrote:       > On Monday, 4 November 2013 21:49:45 UTC, Erland Sommarskog wrote:       >> (rja.carnegie@gmail.com) writes:       >>       >>> But, what should I expect to find where a table was newly       >>> indexed or newly created with a clustered index "ON [INDEX]"       >>> as filegroup?       >>       >> In the [INDEX] filegroup.       >>       >> There are no differences between SQL 2005 and SQL 2012       >> in this regard.       >       > Wow. Was I supposed to know this? :-(       >       > So this script (as I see) puts the table in "INDEX" although       > I specifically said "PRIMARY".       >       > CREATE TABLE rjac20131105a       > (       > i int       > NOT NULL       > CONSTRAINT rjac20131105b PRIMARY KEY ON [INDEX]       > , j int NULL       > )       > ON [PRIMARY]       > ;       >       > Thank you; I'm glad I got around to asking!              That's right. I just confirmed it by testing your script.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca