Viewing 15 posts - 61 through 75 (of 79 total)
Thanks for your response, Gila. Unfortunately, the Job History and SQL Server Error log doesn't reflect much. The only information it gave that the backup log is failed with the...
September 3, 2009 at 3:18 am
You have a full backup of size 1GB. Create a database on the QA environment with the same logical file name as of the Production DB. Restore the database and...
September 3, 2009 at 2:10 am
Which version of SQL Server are you using?
If you are using SQL Server 2008, then you have the ability to trace the change easily.
August 28, 2009 at 5:36 am
Check in SQL Server logs and windows application log. I think you should get some info from there.
Is there any particular activity on the SQL Server when you get...
August 28, 2009 at 5:32 am
I think its normally databasename_log.ldf.
However, could you please be brief on that...
July 7, 2009 at 6:57 am
Nice work... but what was the error you are getting initially?:-)
July 7, 2009 at 6:52 am
I think the preferred way to deal with this situation is to create Custom roles for both the server and the databases.
However, I don't think, its a good practice to...
June 9, 2009 at 7:15 am
you can deploy in any sequence, depending on the version of SQL Server you are going to install.
If you are going to use the SQL Server 2005 Express Edition, I...
June 9, 2009 at 6:11 am
I think you need to change your database recovery model to 'Bulk-logged', before you load the files using SSIS. This is use minimum amount of Transaction log space.Once the file...
June 9, 2009 at 5:40 am
You can also use the Evaluation Edition of SQL Server 2005/2008 for Free.
Microsoft is offering this evaluation copy for 180 days. I think within that period, you will learn how...
June 9, 2009 at 4:35 am
Could you please clarify your question: your database has grown from 42GB to 1.5GB????:w00t:
You can approach the following way:
1. Restore the backup to a new database, say TestDB.
2. Run a...
June 9, 2009 at 4:14 am
Sam,
You need to shrink the Transactional log file on requirement, mostly, when you are running out of space. However, it is adviceable that you should take a log backup before...
May 26, 2009 at 8:40 am
check which log files contains the maximum space, then perform a transactional log backup on that. Once the backup is complete, shrink the log file to some percentage, as per...
May 22, 2009 at 9:01 am
Use the scripts mentioned in the following Ms-KB246133: http://support.microsoft.com/kb/246133/
Once you executed this script, you will able to copy logins from SQL server 2000 to SQL Server 2005.
Once...
May 22, 2009 at 8:52 am
Run the DBCC shrinkdatabase command to shrink your database size. You can also use the DBCC shrinkfile option as well.However, as mentioned earlier, by the other respectable members, you should...
May 22, 2009 at 8:40 am
Viewing 15 posts - 61 through 75 (of 79 total)