Viewing 15 posts - 61 through 75 (of 340 total)
Jones,
Take a transaction log backup and shrink the log file. Regular shrinking is not advisable as it causes fragmentation. Refer this link for more info,
http://www.sqlservercentral.com/Forums/Topic508854-357-1.aspx
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 9:30 pm
No. That link actually describes the procedure to upgrade an existing log shipping configuration from Sql 2000 to Sql 2005. It does not deal with migrating/upgrading from Sql 2000 to...
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 9:20 pm
I don't think that should be a problem..But without changing the compatability I don't think it is possible to use maintenance plan
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 2:45 am
[font="Verdana"]You can make use of the below command to change the database compatability,
sp_dbcmptlevel 'Dbname', 90
Refer this link for more info,
http://msdn.microsoft.com/en-us/library/ms178653.aspx[/font]
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 2:39 am
Inorder to avoid it you need to perform the following,
1. If your database is in Full/Bulk logged recovery model you need to take regular transaction log backups which will truncate...
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 2:34 am
Sethu,
I think you need to change the compatability of your Testdb to 80 or 90. Because the maintenance plan will not be able to backup the Sql 2005 databases which...
[font="Verdana"]- Deepak[/font]
June 3, 2008 at 2:29 am
You need to rebuild the system databases to change the Sql server collation. You can use the below command to perform the same,
start /wait setup.exe /qn INSTANCENAME=”MSSQLSERVER” REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=”XXXX”...
[font="Verdana"]- Deepak[/font]
June 2, 2008 at 7:10 am
Select serverproperty('productversion') will also provide you the desired result. Refer this link for more info,
http://support.microsoft.com/kb/321185
[font="Verdana"]- Deepak[/font]
June 2, 2008 at 7:02 am
If the data changes rapidly in the source database then the snapshot might run out of disk space. If a database snapshot runs out of space, it is marked as...
[font="Verdana"]- Deepak[/font]
June 2, 2008 at 7:00 am
You can verify the validity of your backup file by using the command,
Restore verifyonly from disk='Path\filename.bak'
If the backup file is valid then it can be restored in any other server...
[font="Verdana"]- Deepak[/font]
May 28, 2008 at 10:11 pm
You cannot install Sql 2005 EE in Vista or XP as it requires server OS like Windows 2003 or 2000 etc..However you can install Sql 2005 evaluation edition in both...
[font="Verdana"]- Deepak[/font]
May 27, 2008 at 9:50 pm
Hi Binu,
The restore is similar to normal restore. To restore system databases you need to have the same build and edition of Sql Server i.e example,
If your msdb full...
[font="Verdana"]- Deepak[/font]
May 27, 2008 at 9:35 pm
You cannot install Sql Server 2005 Enterprise edition in your Windows Vista. You need to have a server OS to accomplish the same. Refer this link for system requirements, http://technet.microsoft.com/en-us/library/ms143506.aspx
[font="Verdana"]- Deepak[/font]
May 27, 2008 at 6:39 pm
You can check the Sql Service account in the Sql Server configuration manager. Go to start - run - type 'Sqlservermanager.msc' and hit enter it will open the Sql server...
[font="Verdana"]- Deepak[/font]
May 27, 2008 at 7:34 am
I think SNAC - Sql Server native client. The 1st link is for SNAC and the 2nd is for other components. So you have to apply both.
[font="Verdana"]- Deepak[/font]
May 27, 2008 at 4:12 am
Viewing 15 posts - 61 through 75 (of 340 total)