Anyone out there really know about SQLServer?
-
OK People, can anyone help with this one.......... What we would like to do is have an MSSQL7 database that contains a common set of table. Then depending on the option our customers have purchased attach 1 or more files to it that contain additional tables (anyone still with me?). This would then give me something like: File1. - MSSQL7 System tables. File2. - Our common tables. File3..N - Our service tables. - These are the one that may or may not exist. This then allow us to distribute our service tables pre-populated speeding up the installation for the customer. (Each one may contain 500K+ rows) I didn't want to go down the road of having imports of data and our current system simply attaches (sp_attach) the relent file to the engine - Instant installation. I've tried playing with storage groups/removable databases etc. Setting the default storage group and creating the tables in differnet file. But I cannot quite get the right options. I'm not even sure if what I'm trying to do is possible. It seems that I may need to play directly with the system catalogue to inform it about which tables exist where? Any help/suggestions would be appreciated.
-
OK People, can anyone help with this one.......... What we would like to do is have an MSSQL7 database that contains a common set of table. Then depending on the option our customers have purchased attach 1 or more files to it that contain additional tables (anyone still with me?). This would then give me something like: File1. - MSSQL7 System tables. File2. - Our common tables. File3..N - Our service tables. - These are the one that may or may not exist. This then allow us to distribute our service tables pre-populated speeding up the installation for the customer. (Each one may contain 500K+ rows) I didn't want to go down the road of having imports of data and our current system simply attaches (sp_attach) the relent file to the engine - Instant installation. I've tried playing with storage groups/removable databases etc. Setting the default storage group and creating the tables in differnet file. But I cannot quite get the right options. I'm not even sure if what I'm trying to do is possible. It seems that I may need to play directly with the system catalogue to inform it about which tables exist where? Any help/suggestions would be appreciated.
I don't thin it's possible... It's genarally a bad idea to put datafiles from one server to another server. The servers might be installed with different codepages and/or sort orders, and then your files don't work on the new server. Always do an import from something when installing an application, that uses SQL Server, on a new server. - Anders Money talks, but all mine ever says is "Goodbye!"
-
OK People, can anyone help with this one.......... What we would like to do is have an MSSQL7 database that contains a common set of table. Then depending on the option our customers have purchased attach 1 or more files to it that contain additional tables (anyone still with me?). This would then give me something like: File1. - MSSQL7 System tables. File2. - Our common tables. File3..N - Our service tables. - These are the one that may or may not exist. This then allow us to distribute our service tables pre-populated speeding up the installation for the customer. (Each one may contain 500K+ rows) I didn't want to go down the road of having imports of data and our current system simply attaches (sp_attach) the relent file to the engine - Instant installation. I've tried playing with storage groups/removable databases etc. Setting the default storage group and creating the tables in differnet file. But I cannot quite get the right options. I'm not even sure if what I'm trying to do is possible. It seems that I may need to play directly with the system catalogue to inform it about which tables exist where? Any help/suggestions would be appreciated.
Perhpas you should create a small app that creates the tables via the proper sql and then submits the data to the db. Store the data in a format of your own such as a comma delimeted file.
Todd Smith
-
I don't thin it's possible... It's genarally a bad idea to put datafiles from one server to another server. The servers might be installed with different codepages and/or sort orders, and then your files don't work on the new server. Always do an import from something when installing an application, that uses SQL Server, on a new server. - Anders Money talks, but all mine ever says is "Goodbye!"
Thanks, I thought that may be the answer! Regards, Kevin.
-
Perhpas you should create a small app that creates the tables via the proper sql and then submits the data to the db. Store the data in a format of your own such as a comma delimeted file.
Todd Smith
Thanks, I was looking for the impossible! Regards, Kevin.