Fell virtual server, yesterday raised and moved onto a new backup of 02.12.15 number of backup, whether it is possible to restore the database with a log of the ldf 12.24.15 number
Register and join over 40,000 other developers!
Recent Topics
-
The Game You Are Waiting For?
WendellHarper - Dec 06 2020 01:21 PM
-
Quora and Reddit Backlinks
WendellHarper - Dec 06 2020 01:14 PM
-
Delete account
pindo - Jul 23 2020 01:33 AM
-
Print specific values from dictionary with a specific key name
Siten0308 - Jun 20 2019 01:43 PM
-
Learn algorithms and programming concepts
johnnylo - Apr 23 2019 07:49 AM
Recent Blog Entries
Recent Status Updates
Popular Tags
- networking
- Managed C++
- stream
- console
- database
- authentication
- Visual Basic 4 / 5 / 6
- session
- Connection
- asp.net
- import
- syntax
- hardware
- html5
- array
- mysql
- java
- php
- c++
- string
- C#
- html
- loop
- timer
- jquery
- ajax
- javascript
- programming
- android
- css
- assembly
- c
- form
- vb.net
- xml
- linked list
- login
- encryption
- pseudocode
- calculator
- sql
- python
- setup
- help
- game
- combobox
- binary
- hello world
- grid
- innerHTML

2 replies to this topic
#1
Posted 31 January 2016 - 07:58 AM
#2
Posted 01 February 2016 - 11:10 PM
I don't think you're ready to be a DBA, even a Junior one (sorry!).
Access is ok for end-users just pulling out numbers (similar to how office workers use Excel), but its considered nothing more than a novelty toy in the world of developers and enterprise databases.
I'd really just focus on being a developer with SQL Server first, there is probably a LOT you don't yet understand about T-SQL, let alone having to act as DBA. I think you'd need at least 2 or 3 years of working with SQL before you could realistically move into a DBA role.
--------------------------------------------------------------------------------------------------------------------
Dot net Training in Chennai | Dot net Training in Chennai | Dot net Training in Chennai
#3
Posted 09 February 2016 - 09:31 AM
You may try both variant of restoration:
First powerful resources
http://support.oreil...corrupted?rfm=1
http://itknowledgeex...e-is-corrupted/
https://www.repairto...rverrepair.html SQL Server Repair Toolbox
Check DB
Sometimes when you connect to your database server, you may find it in suspect mode. Your database server won’t allow you to perform any operation on that database until the database is repaired.
A database can go in suspect mode for many reasons like improper shutdown of the database server, corruption of the database files etc.
To get the exact reason of a database going into suspect mode can be found using the following query,
DBCC CHECKDB (’YourDBname’) WITH NO_INFOMSGS, ALL_ERRORMSGS
Output of the above query will give the errors in the database.
To repair the database, run the following SQL Script
EXEC sp_resetstatus ‘yourDBname’;
ALTER DATABASE yourDBname SET EMERGENCY
DBCC checkdb(’yourDBname’)
ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (’yourDBname’, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE yourDBname SET MULTI_USER
Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download