March 25, 2011 at 2:56 pm
So, to preface this...I have a server that I inherited that has a database with three schemas (we'll call them dbo, Admin, Audit).
The server has four main hard disks. One of them (E:) has files that have the name of the Admin schema and a ".Table.sql" extension. So basically there are files that look like this:
Admin.[tablename].Table.sql
So, it made me wonder what they were and I had to wonder if you can have secondary files that are for a table in a named schema? One of them is 2GB so my intial thought is that the schema was just located on a separate drive but if I look at the file locations of the database, there are only two data files. DB.mdf and DB.ndf that are located on F: and G:. So I'm now thinking that they are simply the old output from a conversion of the server. Can a schema have it's own data files or would they have to be in a different filegroup and the filegroup would just be assigned to a different drive?
Any thoughts?
Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/
March 26, 2011 at 6:16 am
Schemas can't have a separate data file but object in the schema can be put on different filegroups which in turn can be put on different drives.
If you've checked sys.master_files and 'Admin.[tablename].Table.sql' files are not listed then they are nothing directly to do with SQL Server.
Have you looked at the contents of the files? If they are very large you could just open a command prompt and type the following to see the first few lines of what they contain. I suspect they are are exports of data.
[font="Courier New"]more Admin.[tablename].Table.sql[/font]
March 28, 2011 at 11:49 am
DNA_DBA (3/26/2011)
Schemas can't have a separate data file but object in the schema can be put on different filegroups which in turn can be put on different drives.If you've checked sys.master_files and 'Admin.[tablename].Table.sql' files are not listed then they are nothing directly to do with SQL Server.
Have you looked at the contents of the files? If they are very large you could just open a command prompt and type the following to see the first few lines of what they contain. I suspect they are are exports of data.
[font="Courier New"]more Admin.[tablename].Table.sql[/font]
Thanks for your response. Turns out it was a data migration script to create the table and insert the data row by row. 😀
Owner & Principal SQL Server Consultant
Im Your DBA, Inc.
https://www.imyourdba.com/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply