recovery mode

we back our network up using veritas backup exec. the
backup fails; it wants me to change the recovery mode from
simple to full. Will this cause problems on my SQL server?You should read in Books Online about backup and recovery models. This is a too big topic to handle
in a newsgroup post. Most probably it will be OK, but if you don't backup log often enough, it might
become quite large.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"ben" <anonymous@.discussions.microsoft.com> wrote in message
news:0c9c01c3af60$edc3a8d0$a301280a@.phx.gbl...
> we back our network up using veritas backup exec. the
> backup fails; it wants me to change the recovery mode from
> simple to full. Will this cause problems on my SQL server?|||Hi ,
It wont create any issues in your SQL Server, Only thing is
take a backup of your Transaction logs based on the transaction volume.
Otherwise since FULL recovary model logs all transaction happening in the
database, which will cause your Log file to grow like any thing.
Thanks
Hari
MCDBA
"ben" <anonymous@.discussions.microsoft.com> wrote in message
news:0c9c01c3af60$edc3a8d0$a301280a@.phx.gbl...
> we back our network up using veritas backup exec. the
> backup fails; it wants me to change the recovery mode from
> simple to full. Will this cause problems on my SQL server?|||To add to the other responses, note that you'll need to perform a full
database backup after changing the recovery model from SIMPLE to FULL.
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"ben" <anonymous@.discussions.microsoft.com> wrote in message
news:0c9c01c3af60$edc3a8d0$a301280a@.phx.gbl...
> we back our network up using veritas backup exec. the
> backup fails; it wants me to change the recovery mode from
> simple to full. Will this cause problems on my SQL server?sql

Records don't lock-one user receives error

I created a MSAccess application with the forms in one db (front end) and the tables in another db (back end). The network admin migrated the back end to SQL Server. With a few minor changes (changing -1 to 1 in queries, etc.) the migration seemed to go pretty smoothly and everything works fine except....

The MSAccess backend used to lock records when someone was editing them. The status of the record was indicated in the record selector on each form, a right pointing arrow to indicate the record was free, a pencil with three dots indicating the record was locked by the current user, and a circle with a diagonal line to indicate the record was locked by another user. When 2 users attempted to simultaneously edit a record, the first user got the lock on the record. The second user received a message as soon as they attempted to edit the locked record to the effect that the record was locked.

Now (since the migration to SQL Server) the record selectors no longer give any indication as to the locking status of the records. When 2 users attempt to simultaneously edit a record, both are able to enter information in their forms, but when the second user attempts to save the record they receive the following message:

This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made. Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make changes.

Please help me find the cause of this behavior. Is it something I need to change in the MSAccess front end or something that needs to be set in the SQL Server back end by the network admin?

I am moving this question to the SQL Server Database Engine forum.