Kind of Replication will work ?

HI
We have 1 Central office Corporate Office and three branch offices. We
are in process of developing an Order Management Application, Every
branch will enter Inquiries/Quotation/Orders into application and at the
end of day we want all data entered at every branch to be available at
corporate office for further processing, can you please advise me kind
of replication will work for us. Thanks in advance
Best Regards
Shahid Saleem
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
It looks like you only want data flowing one way, from the branch offices to
the central office. In this case I would use transactional replication.
The next question you have to ask your self is, is there anything unique
about your data in the branch office which makes it identifiable as
belonging to that branch? If so, you should filter on this data, and when
you are in the specify articles dialog for the publication, click on the
browse button to the right of your table name, select the snapshot tab, and
select the delete all data in the existing table that matches the row filter
statement.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Shahid Saleem" <shahid_mcsd@.hotmail.com> wrote in message
news:e3l4fOx8EHA.2568@.TK2MSFTNGP10.phx.gbl...
> HI
> We have 1 Central office "Corporate Office" and three branch offices. We
> are in process of developing an Order Management Application, Every
> branch will enter Inquiries/Quotation/Orders into application and at the
> end of day we want all data entered at every branch to be available at
> corporate office for further processing, can you please advise me kind
> of replication will work for us. Thanks in advance
> Best Regards
> Shahid Saleem
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

Killing automatically crashed sessions ??

If one of my workstations (which communicate using ODBC) crashes, I still see it as connected in Enterprise Manager under management\current activity\.
Is there anyway to kill automatically the crashed cessions?
Thkx in advanceYou could periodicaly scan the sysprocesses table and kill any connection that hasn't had activity in some predeturmined amount of time.

Key Management Utility

We are getting our arms around best practices for data encryption using SQL
Sever 2005. We can (and have) implemented data encryption via certificates
under the following guidelines using the scripting available through SSMS.
http://www.microsoft.com/technet/it.../sqldatsec.mspx
One of our internal guidelines mandates three factor authentication for the
encryption keys that must be changed every 90 days.
Is there a key management utility available that could aid in this process
or will we need to develop our own using the scripting comands?
TIA,
- Marc CastrechiniDear Marc,
From your description, I understand that:
Your SQL Server 2005 is using data encryption by certificates. Due to your
company's policy the keys must be changed every 90 days, so you want to
know if a key management utility existed can help you on this process.
If I have misunderstood, please let me know.
If they want to use new certificate, you need to manually write script to
remove the old certificate and add the new one. Also, you need to get the
symmetric keys protected by certificates before they drop the old
certificate. There is no tool in SQL 2005 to do this automatically. You
can consider to create a job to run the script.
Also, you may use self-signed certificate which is not related to with
certificates issued by CA at all.
For more information, you can refer to:
http://www.microsoft.com/technet/it.../sqldatsec.mspx
Sincerely,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions?
I will appreciate your posting back for further research if this issue
perists.
It's always my pleasure to be of assistance.
Sincerely,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============

Keepin my windows open in Management Studio

It's a wonderful convenience for me to open up a Mgmt Studio project and have all the windows come up that I had when I closed it. I tried saving everything as a project before I closed. This morning, the desired result happened when I opened Mgmt Studio and opened the project: all my windows were open just like I left! It was wonderful! So I worked, saved the project before I closed out again. When I reopened later, the windows didn't come up again.

Can anyone give me advice on a step I may be missing? Since it happened once, I know it can be done.

Btw, I have upgraded my client tools to SP2.

Thanks in advance!

You can create your own shortcut for SSMS and add whatever additional arguments you choose based on the command line options for sqlwb.exe. You can look up the options in books online under the topic sqlwb utility. Or the online version of this help topic is at: http://technet.microsoft.com/en-us/library/ms162825.aspx

-Sue

|||

Thank you for your response. However, I cannot find any switch to remember which windows I had open at the time of closing. I was hoping to find something to how VS operates in that everytime I open it, it opens exactly the way I left it.

|||

Not it doesnt unless it crashes and manages to recover the files which were open. Please fell free to post a suggestions on the http://connect.microsoft.com site.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Thank you for the response. It's not the answer that I wanted, but it is the answer.

Keep registered servers in tact

Every time I register servers in Management Studio, the next time I reopen management studio after closing it, they all disappear. Is there a setting somewhere to tell SSMS to keep those settings?Hmmm... That's strange. The data for registered servers is stored in C:\Documents and Settings\%User%\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\RegSrvr.xml take a look at that file between sessions.

Keep prior select results in the Results pane

I run query A in SQL server (Management Studio). I slightly change the query and want to run it again. How do I keep the results of the prior run in the Results pane so that I can compare them.

Thanks,

Skender

You can open mulitple query Windows to do that, or just copy the results out to another window.

Buck Woody

|||

Oracle had a code you put in and saves the results in the same window (spool on). I was hoping SQL server has the same thing.

Keep a few connections open all the time or open/close connections on the fly?

Just a quick question about connection management. My application will
never need more than 1 or 2 connections about at any given time. Also, I do
not expect many users to be connected at any given time. For efficiency, I
would like to keep connections alive throughout the lifetime of the objects
requiring them, rather than opening a new connection, executing code and
then closing it again. What is the most efficient way of doing this?
Should I perform the open/close or just one open when I create the object
and a close when I dispose of it?Robin Tucker (r.tucker@.thermoteknix.com) writes:
> Just a quick question about connection management. My application will
> never need more than 1 or 2 connections about at any given time. Also,
> I do not expect many users to be connected at any given time. For
> efficiency, I would like to keep connections alive throughout the
> lifetime of the objects requiring them, rather than opening a new
> connection, executing code and then closing it again. What is the most
> efficient way of doing this? Should I perform the open/close or just one
> open when I create the object and a close when I dispose of it?

First of all, what client library are you using?

Some client libraries, ADO and ADO.Net employs connection pooling, so
when you officially disconnects, the client library actually keeps the
connection around for some 60 seconds, in case you like to reuse it.
Connection pooling can be quite essential in web applications.

If you are writing a VB application and you know you will never have
any users connected, I don't see anything wrong in creating a connection
and keep the connection object alive as a global variable.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp