Re: msmq to sql?
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 23:58:33 -0400
All these for 1) asynchronous access and 2) for security.
Well that depends on what you are doing. Asynchronous access to a database is not very useful for most user applications. If you are only talking about SQL Server as a back end to an app that just needs to load data such as a logging process this may be fine. But if it is a user interface app and the user expects to see data back these techniques don't work well. Don't get me wrong things like Service Broker have a definite place and work great for what they were designed to do. But you can't front end a database server with these tools and expect them to work like a database server. I just got off a large project where we had to completely rewrite an app that made extensive use of web services because it couldn't scale as written and simply was the wrong tool for the job in this case. Management needs to define what their goals are first and then decide what the best tools for the job are, not the other way around.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Andy" <kc2ine@xxxxxxxxx> wrote in message news:%23y6juKOHIHA.4880@xxxxxxxxxxxxxxxxxxxxxxx
I have 2005 version. I was thinking about mirroring also,
but management wants to have some kind of user separation from SQL server like web service (I don't want to do this) or messaging services like MSMQ or SQL 2005 server Broker Agent. All these for 1) asynchronous access and 2) for security.
So I'm a little confused what to use. What would you guys suggested?
thanks
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message news:O9IdyLJHIHA.6044@xxxxxxxxxxxxxxxxxxxxxxxWhat happens then when the server that is running msmq goes down? Why would you think that would be more reliable than SQL Server? MSMQ can't even begin to duplicate the functionality of SQL Server and should never be thought of as a backup to or replacement for it. You are better off looking at valid HA or DR means for SQL Server such as Clustering, Database Mirroring, (possibly replication), Log shipping etc. But your goals and business needs will dictate the actual methods used.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Andy" <kc2ine@xxxxxxxxx> wrote in message news:u%23%23CdMEHIHA.1316@xxxxxxxxxxxxxxxxxxxxxxxHi,
If I'd like to ensure that in case sql server is down user still can access and write the the data what option do I have? Since writing is more important I thought about MSMQ tu put between the server and the application, but what about reading? Any other techiniques?
In case of MSMQ, can you suggest any example how to use it with SQL server?
thanks
.
- Follow-Ups:
- Re: msmq to sql?
- From: Andy
- Re: msmq to sql?
- References:
- msmq to sql?
- From: Andy
- Re: msmq to sql?
- From: Andrew J. Kelly
- Re: msmq to sql?
- From: Andy
- msmq to sql?
- Prev by Date: Permission denied in ASP.NET 2.0 with IE
- Next by Date: Re: msmq to sql?
- Previous by thread: Re: msmq to sql?
- Next by thread: Re: msmq to sql?
- Index(es):
Relevant Pages
|