Alterations to published website

Hi,
Your first question was at one time a real nightmare...
Databases used to create a lock.
But no longer.

You now have what is referred to as Optimistic Concurrency.
http://msdn.microsoft.com/en-us/library/ms171845.aspx

Your question about the Web Admin tool is too vague.
Can't really help without more info but can say Yes, what you need can be done.

Yes unless you lock records multiple user can login and the same user is already logged in.

The Database may be less scary than you currently think it is.
Salute,
Mark

 

Thanks a lot- can I assume optimistic concurrency is turned on?


Reading the article, it seems to be addressingpart ofwhat I am asking (users altering data at the same time).


But I was not sure if it addresses the situation of me opening a connection and opening atable on my end and editing a row. Or especiallywhat happens to users ifI alter the database structure by adding columns to a tableor modifying a data type? What if I am in there creating a new table that is not referenced by the web application (yet)?


I am asking about limits to doing backend work while the application may be in use.

 

In the most simple of terms the SQL Server will handle this for you.


Unless a function, query, etc, bombs out with an error.
Even then you should not have any problems with the actual data.


There are entire chapters you can write about these transactions but for the most part you're covered.
Salute,
Mark

 

Thanks very much. Here's hopin it all works...

 

Hi, I was wondering what I can get by with doing tomy database and sitewithout disturbing customers. For example, if I open a connection to the sql database, will that screw up users?

If I open a particular table, will thatdisrupt all users, or just the users who happen to be reading/writingto that specifictable?

If I add columns to a table, will that screw up users, assuming that the application doesn't reference the new column yet?

If I do an update to an aspxpage, and copy it to the server, will that bother everyone?
How about those people who happen to be looking at that page? What would they experience?

Last, I used the Web Admin tool to add users who have specific privileges.Do I access that the same,now that the survey is in production?

What if two people log in as the same user at the same time. Would there be a problem with that?

: ) sorry for the flurry of questions.