After installation of SP3a on the publication server, clients are getting
errors during replication.
The error detail is : "Select permission denied on object
'MSDistributor_access', database 'tempdb', owner dbo
does this table exist in tempdb?
"Nol Thoelen" <noel.thoelen@.itomni.be> wrote in message
news:407bdf20$0$876$a0ced6e1@.news.skynet.be...
> After installation of SP3a on the publication server, clients are getting
> errors during replication.
> The error detail is : "Select permission denied on object
> 'MSDistributor_access', database 'tempdb', owner dbo
>
>
|||Yes, the table does exist in the tempdb database
"Hilary Cotter" <hilaryk@.att.net> schreef in bericht
news:erRWAPXIEHA.2596@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> does this table exist in tempdb?
> "Nol Thoelen" <noel.thoelen@.itomni.be> wrote in message
> news:407bdf20$0$876$a0ced6e1@.news.skynet.be...
getting
>
Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts
Friday, March 30, 2012
Friday, March 23, 2012
Replication Configuration Helper (Id buy it!)
Let's face it - setting up SQL 2005 merge pull replication using HTTPS between numerous SQL Server 2005 Express clients and one or more Publishers is an overly complicated exercise.
It should be easy. Why is it so hard?
In a nutshell: The connection chain and security chain is long and when there's a problem the error messages just don't point you to the answer - You have to search for it;re-read the doco; talk to gurus; use logging tools;re-read the error message 100 times; etc. etc.
It should be possible to create a 'Replication Configuration Helper' that steps -step by step - through both the connection chain (App - to SQL Express - to local network components - to the TCP/IP network - to the web server - to the publishers/distributers) and through the security chain (App - to SQL Express authentication - local agents including certificate errors - to ISS server authentication - to Distributer authentication -to Publisher authentication to Article authentication).
Let's face it - the steps occur in sequence and each step can be tested and the appropriate error message raised - TOGETHER WITH INSTRUCTIONS ON HOW TO RESOLVE! (I mean - what's use is an error message when you have to cut and past the error message into a browser and search for ages before you get the instructions on how to resolve the problem?)
So c'mon - someone volenteer to write a 'Replication Configuration Helper'
Monday, February 20, 2012
Replicating specific data
Hi All,
We are in healthcare domain and we have a complete package written in VB6
and SQL Server 2000. We have installed in one of our clients. This client is
actually part of a chain of hospitals. Each hospital can have patients
registered with them. Also, this patient could also go to other hospitals
within the chain.
My question is, What is the best way to share the patient information. One
option would be to have a central repository. Another option would be for
the hospital to request for the patient information from the hospital he was
registered with. Is this possible. Can I just replicate a specific patient
information data. We are looking for the cheapest solution. Right now, we
are planning to give each hospital within the chain, a location code and
patient ID will be generated with this code prefix.
Also, what are the options for me to send this data across.
Any advise, please...
Raju
You could use replication for this, but you will have to handle data
ownership. So if you replicate patient data from a central repository to a
branch office and make changes to it there, do you want it to stay at the
branch office, or do you want these changes to go back to the central
repository.
What criteria would cause data to flow? For instance what event would
trigger data to move to the branch office from the central repository. What
portion of the data would move? Would it be a subset of the data, or the
entire history. For instance accounting data could probably stay, but his
vitals, and medical history would have to be copied.
I think you will find that most of your data would have to be global. In
this case a remote access option where everyone connects to the central
repository via terminal services, or a web application would probably work
best.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Raju Joseph" <vze24srd@.msn.com> wrote in message
news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> We are in healthcare domain and we have a complete package written in VB6
> and SQL Server 2000. We have installed in one of our clients. This client
> is actually part of a chain of hospitals. Each hospital can have patients
> registered with them. Also, this patient could also go to other hospitals
> within the chain.
> My question is, What is the best way to share the patient information. One
> option would be to have a central repository. Another option would be for
> the hospital to request for the patient information from the hospital he
> was registered with. Is this possible. Can I just replicate a specific
> patient information data. We are looking for the cheapest solution. Right
> now, we are planning to give each hospital within the chain, a location
> code and patient ID will be generated with this code prefix.
> Also, what are the options for me to send this data across.
> Any advise, please...
> Raju
>
|||Unfortunately, that can't be answered. You have very strict privacy
requirements as well as very strict controls on the data. Before you can
start looking at putting in an infrastructure to distribute data, you first
have to find out whether you even can and if you can, what business rules
does it need to be governed under. That is going to tell you whether you
have a central repository or whether you are distributing data. It will
also tell you if changes to the data is allowed at multiple locations.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Raju Joseph" <vze24srd@.msn.com> wrote in message
news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> We are in healthcare domain and we have a complete package written in VB6
> and SQL Server 2000. We have installed in one of our clients. This client
> is actually part of a chain of hospitals. Each hospital can have patients
> registered with them. Also, this patient could also go to other hospitals
> within the chain.
> My question is, What is the best way to share the patient information. One
> option would be to have a central repository. Another option would be for
> the hospital to request for the patient information from the hospital he
> was registered with. Is this possible. Can I just replicate a specific
> patient information data. We are looking for the cheapest solution. Right
> now, we are planning to give each hospital within the chain, a location
> code and patient ID will be generated with this code prefix.
> Also, what are the options for me to send this data across.
> Any advise, please...
> Raju
>
|||Actually the majority of my clients are in the health care industry.
Replication is huge there, especially in the SQL CE space.
For example a doctor goes into the office and picks up a his pocketPC from
its cradle which has complete information about the patients he is going to
see that day. While he sees the patient and makes entries in the chart the
entries in the Medical Record are synchronized with the central office. His
appointment schedule is updated, certain actions he does are sent to the
clinic's front desk for processing (for example he requires tests, exams,
blood work, etc). Replication is the engine here.
There are mobile medical clinics which see patients in the field (nursing
homes, community centers, etc). Patient records are transferred to these
mobile clinics, and insurance information (especially MediCal, MediCare, and
Social Security) is checked and verified. At night it is sync'd back.
Again replication is the engine.
There are many pharmaceutical industries which receive data nightly and
process it for the morning and then send it back to hospitals. Replication
again is the engine.
All this is done with strict regard to regulatory compliance, privacy
concerns, and HIPPA.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:O9zfYJIGGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Unfortunately, that can't be answered. You have very strict privacy
> requirements as well as very strict controls on the data. Before you can
> start looking at putting in an infrastructure to distribute data, you
> first have to find out whether you even can and if you can, what business
> rules does it need to be governed under. That is going to tell you
> whether you have a central repository or whether you are distributing
> data. It will also tell you if changes to the data is allowed at multiple
> locations.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Raju Joseph" <vze24srd@.msn.com> wrote in message
> news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
>
We are in healthcare domain and we have a complete package written in VB6
and SQL Server 2000. We have installed in one of our clients. This client is
actually part of a chain of hospitals. Each hospital can have patients
registered with them. Also, this patient could also go to other hospitals
within the chain.
My question is, What is the best way to share the patient information. One
option would be to have a central repository. Another option would be for
the hospital to request for the patient information from the hospital he was
registered with. Is this possible. Can I just replicate a specific patient
information data. We are looking for the cheapest solution. Right now, we
are planning to give each hospital within the chain, a location code and
patient ID will be generated with this code prefix.
Also, what are the options for me to send this data across.
Any advise, please...
Raju
You could use replication for this, but you will have to handle data
ownership. So if you replicate patient data from a central repository to a
branch office and make changes to it there, do you want it to stay at the
branch office, or do you want these changes to go back to the central
repository.
What criteria would cause data to flow? For instance what event would
trigger data to move to the branch office from the central repository. What
portion of the data would move? Would it be a subset of the data, or the
entire history. For instance accounting data could probably stay, but his
vitals, and medical history would have to be copied.
I think you will find that most of your data would have to be global. In
this case a remote access option where everyone connects to the central
repository via terminal services, or a web application would probably work
best.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Raju Joseph" <vze24srd@.msn.com> wrote in message
news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> We are in healthcare domain and we have a complete package written in VB6
> and SQL Server 2000. We have installed in one of our clients. This client
> is actually part of a chain of hospitals. Each hospital can have patients
> registered with them. Also, this patient could also go to other hospitals
> within the chain.
> My question is, What is the best way to share the patient information. One
> option would be to have a central repository. Another option would be for
> the hospital to request for the patient information from the hospital he
> was registered with. Is this possible. Can I just replicate a specific
> patient information data. We are looking for the cheapest solution. Right
> now, we are planning to give each hospital within the chain, a location
> code and patient ID will be generated with this code prefix.
> Also, what are the options for me to send this data across.
> Any advise, please...
> Raju
>
|||Unfortunately, that can't be answered. You have very strict privacy
requirements as well as very strict controls on the data. Before you can
start looking at putting in an infrastructure to distribute data, you first
have to find out whether you even can and if you can, what business rules
does it need to be governed under. That is going to tell you whether you
have a central repository or whether you are distributing data. It will
also tell you if changes to the data is allowed at multiple locations.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Raju Joseph" <vze24srd@.msn.com> wrote in message
news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> We are in healthcare domain and we have a complete package written in VB6
> and SQL Server 2000. We have installed in one of our clients. This client
> is actually part of a chain of hospitals. Each hospital can have patients
> registered with them. Also, this patient could also go to other hospitals
> within the chain.
> My question is, What is the best way to share the patient information. One
> option would be to have a central repository. Another option would be for
> the hospital to request for the patient information from the hospital he
> was registered with. Is this possible. Can I just replicate a specific
> patient information data. We are looking for the cheapest solution. Right
> now, we are planning to give each hospital within the chain, a location
> code and patient ID will be generated with this code prefix.
> Also, what are the options for me to send this data across.
> Any advise, please...
> Raju
>
|||Actually the majority of my clients are in the health care industry.
Replication is huge there, especially in the SQL CE space.
For example a doctor goes into the office and picks up a his pocketPC from
its cradle which has complete information about the patients he is going to
see that day. While he sees the patient and makes entries in the chart the
entries in the Medical Record are synchronized with the central office. His
appointment schedule is updated, certain actions he does are sent to the
clinic's front desk for processing (for example he requires tests, exams,
blood work, etc). Replication is the engine here.
There are mobile medical clinics which see patients in the field (nursing
homes, community centers, etc). Patient records are transferred to these
mobile clinics, and insurance information (especially MediCal, MediCare, and
Social Security) is checked and verified. At night it is sync'd back.
Again replication is the engine.
There are many pharmaceutical industries which receive data nightly and
process it for the morning and then send it back to hospitals. Replication
again is the engine.
All this is done with strict regard to regulatory compliance, privacy
concerns, and HIPPA.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:O9zfYJIGGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Unfortunately, that can't be answered. You have very strict privacy
> requirements as well as very strict controls on the data. Before you can
> start looking at putting in an infrastructure to distribute data, you
> first have to find out whether you even can and if you can, what business
> rules does it need to be governed under. That is going to tell you
> whether you have a central repository or whether you are distributing
> data. It will also tell you if changes to the data is allowed at multiple
> locations.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Raju Joseph" <vze24srd@.msn.com> wrote in message
> news:%23gYvlIAGGHA.3856@.TK2MSFTNGP12.phx.gbl...
>
Subscribe to:
Posts (Atom)