Greg, In MS SQL server 2000 you can have up to 16 instances installed on the one PC.
In essence, and Instance is another SQL Server. Example: My computer name is "SERVER", then the default instance (or SQL SERVER) would be referred to as SERVER when configuring the connection details in your application. Inside that SQL Instance we can have many databases. When one installs Pracsoft, you must have an Instance (2nd SQL Server installation potentially....I'll qualify that later) called "SERVER\HCNSYSTEM". The 3rd installation of SQL server in that PC would be called "SERVER\<instancename>" whatever you want to call it. So when configuring your application to talk to an SQL server you would refer to its Instance. Each of them can be stopped and started independently as they are all individual SQL servers. Qualifying that statement before, one can install the 1st installation of SQL server on a PC and call it "SERVER\HCNSYSTEM". We can have an situation where the default Instance "Server" is SQL 7.0 We can have out 2nd Instance as SQL 2000 Service Pack 2. We can have our 3rd Instance as SQL 2000 Service Pack 4. I suspect, but haven't tested it yet, but our 4th Instance could probably be SQL 2005. Oracle and other products in the same vein have a similar strategy available. I hope that clears it up. Regards Barry Lollo -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Twyford Sent: Wednesday, 1 February 2006 2:42 PM To: General Practice Computing Group Talk Subject: Re: [GPCG_TALK] File repair utility in MD2 Cedric Meyerowitz wrote: > Another user made following comments on another forum www.ausgp.com > > "I am of the belief that this was due to the lack of knowledge of the > MSDE product by the programmers at HCN. I believe that they falsely > understood that there is a 2GB per instance limit on MSDE. This is > obviously not the case. There is a 2Gb per database limit, but some > 64K databases per instance which equates to a maximum of 64K x 2GB = 128Tb data per MSDE instance. > > I know of other clinical software providers that aren't interested in > using MSDE to it's full capacity, with a believe that either the > mystical 2GB limit or the concurrency governing restrictions would > have a substantial impact on a large practice. I believe that BP's > programming shows this to be incorrect as BP seems to be happily > running on MSDE in large practices with large databases. " > > As you can see the 2GB limit problem is not a problem. Hence BP has > had no problems in large practices because Frank did his homework and > hence is a better programmer. > > It is important that we do not spread this false rumour of the 2GB > limit, because we then show users we know as little as the scaremongers. > > Cedric Cedric, That is very interesting information about MSDE. I recall going to the Microsoft site to research the MSDE versus MS SQL question and coming away with the sense the '2GB per database' limit for MSDE meant what it sounded like. This concept of instances is new to me, and from your quotation seems to nearly equate to tables in a DB, or rows in spreadsheet. I'd be interested to know what an 'instance' in a 'database' actually means in SQL-speak. If it means that a 'database' in the sense I understand it - in this context all the data one would enter into MD3 - can be a lot more than 2GB in total - then fine. It still seems odd that MS would allow a very large DB with very limiting restrictions on the number of users, in the context of having MSDE as a teaser for their 'full-sized' product. Maybe the fuzziness over the 2GB limit has been primarily for the purpose of encouraging uptake of MS SQL. Greg -- Greg Twyford Information Management & Technology Program Officer Canterbury Division of General Practice E-mail: [EMAIL PROTECTED] Ph.: 02 9787 9033 Fax: 02 9787 9200 PRIVATE & CONFIDENTIAL *********************************************************************** The information contained in this e-mail and their attached files, including replies and forwarded copies, are confidential and intended solely for the addressee(s) and may be legally privileged or prohibited from disclosure and unauthorised use. If you are not the intended recipient, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication or any action taken or omitted to be taken in reliance upon this message or its attachments is prohibited. All liability for viruses is excluded to the fullest extent permitted by law. *********************************************************************** _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
