Andrew Jackson
Forum Replies Created
-
Posts
-
Use the backup history tables in msdb to retrieve the filename and path of the most recent backup.
What happens if you turn off OLE DB Resource Pooling?
'For SQLOLEDB provider 'strConnect = "Provider=SQLOLEDB;server=MyServerName;OLE DB Services = -2;uid=AppUser;pwd=AppUser;initial catalog=northwind" ' For MSDASQL provider 'strConnect = "DSN=SQLNWind;UID=Test;PWD=Test; OLE DB Services= -2"Login details are stored in the master, so it makes sense that they would be gone if you’ve replaced the master database files.
Do you have a copy of your old master.mdf and .ldf file, or did you overwrite them? If not, you will have to recreate all the loginsIf you see a service but it is stopped, start it by right hitting start,
If you do not see a SQL Server service, it is likely you did not install the Server Tools during the install. In this case you need to reinstall with the server tools.
What version Of SQL Server are you ruinning? If you are using 2008 think about using the MERGE command and SSIS to move data from your one server to the other. MERGE is a new feature and will allow you to insert, update and delete all in one command as long as you have good primary keys
use this script to recover database from suspect mode
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_USERTry this:
ALTER DATABASE corrupted_db SET SINGLE_USER WITH ROLLBACK IMMEDIATE DBCC ChECKDB ('corrupted_db', REPAIR_ALLOW_DATA_LOSS) ALTER DATABASE corrupted_db SET MULTI_USERbut there is very high chance of data loss
1. Run DBCC CHECKDB, make sure all the tables are having a clustered index (physical order of records)
2. If you need to restore the database, it may be save to restore just the db, if not many files have changed or any extensions has been upgraded since.
SQLite database format trades space efficiency for speedy access. If you just dump the data contents, either as SQL dump or simply a CVS file for each database table, you’ll likely get smaller files, either using database files or plain data, try compressing them.
No you can’t, However you can use logs to fetch and see the fetched data in logcat or set some value on your textviews or use table layout to see your fetched data.
The simple recovery model is generally appropriate for a test or development database. However, for a production database, the best choice is typically the full recovery model, optionally, supplemented by the bulk-logged recovery model. However, the simple recovery model is sometimes appropriate for a small production database, especially if it is mostly or completely read-only, or for a data warehouse.
Some of reason was these:
CDC (Change data capture)
Point in Time
Database Mirroring
Log shipping
Create Transaction log backup (for critical data)On what kind of a server?? What kind of hardware to serve those files? What kind of disks, network etc.??
First things first. Let’s get you connected. When you installed SQL Server, did you name the instance <your computer name>\SQLExpress ? I would try and choose Windows Authentication as your authentication and then simply place a period (.) in the servername and hit connect.
If that does not work, go to Control Panel/Administrative Tools/Services and make sure the SQL Server Service is running.
SQL Injection occurs when the user of an application is able to affect the meaning of database query. This often occurs when arbitary strings from user input are concatenated to create SQL which is fed to the database
Use the following Data Source “C:\temp\database.sdf;Password=mypassword” to open an encrSQL Server Compact edition file but you must know the password and add that to the connection string.
I hope this helps you:
Alter database <databasename>set Recovery simple
USE <databasename>
DBCC SHRINKFILE (<log_name>, 0, TRUNCATEONLY)
GO
Alter database <databasename> set Recovery fullIn SQL Server, to DELETE a log file in SQL Server just click on OBJECT EXPLORER and connect to the SQL Server database engine then expand DATABASES and right click on the database to which log file you have to delete and then click on properties and select the file page.
NOW, In the DATABASE FILES grid, select the file to delete and then click on REMOVE then click OK.PS: The file must be empty before it can be delete.
After the BLOBs deletion, The BLOB which gets deleted is not a part of the transaction log, hence unable to recover BLOB by just analyzing the transaction log. Therefore INSERT log record is need to manage as well as to recover the deleted BLOB from transaction log using fn_dblog.