Sql DMO on Workstations
-
I am a 20+ year Programmer that only 2 years ago discovered the Joys of VB.
I have written a large Medical app for use in networks with an average workstation load of 40 to 60. I have a couple of routines i included from the samples MS kindly provided to help in automating the discovery of instances of Sql in the network. ( I envision at least one Replication of the server ) if Primary goes down I want User level persons to be able to select from an Options page dropdown that populates with running instances of Sql. The redist file that came with the server software indicates all I need is sqldmo.dll and one file to be included in the sys32 file. Problem 1.
redist.txt and the code notes for the samples are Obtuse. it gives no help at all for discovery of why the code only works in a machine that has either sql server running or on a machine that has all the client/management tools.
Problem 2.
The two dll's it says to redistribute will not register on the client machines and there is no indication as to why.
Can anyone point me in the correct path to find such information? I read thru all these forums and although several questions were simmilar, they were either not complete or just not simmilar enough to answer me..
Comming from a COBOL background some of what is obvious to Others is hidden for me.
I have classic Inline code blindspot syndrome 🙂
Robert Dunlap
Robert Dunlap
http://www.codesonly.com
http://www.vbonly.com -
Im surprised your installed didnt pick up any other dependencies. I'd suggest starting with Depends.exe (including in Visual Studio) - point to sqldmo.dll and it will show you all dependencies. Not quite an answer, but maybe will help clear the fog some.
That said, Im not sure that I agree with what you're proposing. You're really trying to take a shortcut to having a failover server. If you use merge replication I think it'll work, but why have the user pick? Even if they do pick, how will they know if that particular server has a copy of the db they need (and they probably dont know which db they need). I think you'd better off to have some kind of configuration where if server1 doesnt respond, you try server2, 3, etc. Have to figure at some point there will be other SQL boxes on the network that have nothing to do with your app.
Andy
-
Many thanks for the quick response. Like I said I am very much a Newbie in VB, I have lots of Good friends on the web who have No idea of the higher complexitys of Multi user Networked data apps. I am much newer to Sql even than VB. Your advice seems very sound. Can you Elaborate? I have used MSDE extensively since begining with Sql, and find it to be very adequate if a little Obtuse with the explanations.... ("Grasshopper has many questions Master")
I have chose to use Named instances ( named specifically for the app ) and that was cludgy, now am looking at just querrying for all Sql servers, then looking for my database and if its there add server to the list to choose from. I have over the last several months bought many Great Sql books and they help immensely but a good discussion of the topics that are critical for my app are just not there.
I am reading on Triggers and Stored proceedures currently and looking at making the Sql Server do much more of my Data mining ( with an eye at thinning my client network usage Dramatically ), do you have the time to engage in some discussion with a Newbie on these subjects? most of the reasoning behind my choices so far are limited to one primary consideration. I dont have enough knowledge of the proposed platform diversitys to adequately support the app if i did somehow find enough resource to code it right.
this forum was highly recomended by several of my site users, and so here is "Grasshopper" seeking advice from the pro. Robert Dunlap
ps ( I have never used Depends, silly I know but self taught in the language gives me some natural defeciencys in the art of good code )
Robert Dunlap
http://www.codesonly.com
http://www.vbonly.com -
We don't mind beginner questions, all we ask is that you try to figure it out for yourself first! I'd recommend you that you post bite sized questions that are fairly narrow in scope.
Your plan of searching all the instances for your db name will work (unless someone else has already created a db with the same name, not impossible). Not sure it's worth the work to implement. Downtime for a SQL box is usually minimal and if it's that important the DBA or network admin will be the ones responsible for having a fail over plan in place. My opinion, others may disagree!
Before you venture into data mining I think you'll want to fully exploit stored procedures, triggers, views, and functions - things in SQL that will help you reduce round trips to the server and reduce bandwidth usage, all things that will make your app sturdier and more responsive.
Finally, what you you using to install your application? It's generally easier to let the installer figure out what needs to be distributed, then just figure out if you are allowed to redistribute them.
Andy
-
Well with that said I suppose that in order for you to give me the best advice you will need to know a few details of the objective i am trying to reach.
the app is a complete Patient Management system for a small to medium sized Medical Center and for the Doctors Office/Clinic. Its devided into several Logical Grouped feature sets. I began the project with a known incomplete picture of where i needed to end up. so i didnt start with triggers, Stored proc's and such, instead i went with my app manageing all the data interaction until such time as some of the features became concept complete. now I am prepairing myself for the process of making Sql do more of what it was intended.
in a doctors office you will rarely find a Data admin, ( hehe ) you in fact will rarely find anything but User level persons. that is my need for user to select in a list from available instances of my database. Its Unlikely although possible to run into a situation where the database name is used so I plan to count on its uniqueness ( with a qualifyer.) i have one field in one table that will be my validation of the server/database. Is there another industry accepted Methodology to achieve that?
I will keep my questions in scope and size to make this more profitable to everyone.
I agree with your data mining statement. ( i was using it erroneously ) I did my description above so we would be on the same page. once again it comes down to not being qualifyed to ask the proper question ;).
I am currently using the built in Install builder for VB, but as release time gets closer we will be going to Wise Install builder :).
Robert Dunlap
Robert Dunlap
http://www.codesonly.com
http://www.vbonly.com -
I left out one small detail in my last post.
one of our primary objectives is for the physician to have the ability to have our setup in his office if the hospital has it, and allow him to use his portable device to interact with both locations. that is the feature that made me begin looking at DMO in ernest.
Robert Dunlap
Robert Dunlap
http://www.codesonly.com
http://www.vbonly.com -
So you're assuming they will have a box running SQL? Or if they don't, will you rely on MSDE?
Andy
-
Yes, Sql 2000 will be a part of our Setup to the customer. Predeployed on a platform and ready to plug and integrate to existing network. For a Doctors office we are planning to use MSDE to house the database.
Robert Dunlap
Robert Dunlap
http://www.codesonly.com
http://www.vbonly.com
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply