Viewing 15 posts - 1,036 through 1,050 (of 1,179 total)
In adition to the above, you can also caputre SQL Profiler from remote machine to capture the activity on the affected server which help you to narrow down the problem...
November 18, 2008 at 4:12 am
What command you were using for SQL 2000?
You can use following command in sql 2000 & 2005
DBCC SQLPERF (LOGSPACE)
November 17, 2008 at 5:00 am
BOL is also excellent source!!! just go through chapter vise i.e. Topic wise. It will give indepth knowledge.
November 17, 2008 at 4:50 am
If you would like to move sys DB from one server to another you can think about attach and detach option too. 🙂
November 17, 2008 at 3:44 am
Officially Logshipping was introduced from SQL Server 2000 only. But surely we can create job to do the same thing in 6.5 & 7.0 with creating customized jobs/SP.
Also one more...
November 17, 2008 at 3:38 am
Robert,
In deed looks very strange.
Does your new SQL Server installation goes well without any problem? Have you created test DB and test?
If new installation is working fine:
As you mention...
November 17, 2008 at 2:58 am
In addtion to this; NO NEED TO WRITE ANY VBS script. 😉
November 13, 2008 at 11:36 pm
If you are using sql 2005 you can do it by creating "Maintenance Cleanup Task" for Backup files. specify the location and extention of file and retention period. Also retention...
November 13, 2008 at 11:34 pm
First you can check your CPU & MEMORY is sufficient to take a load.
November 13, 2008 at 7:03 am
Reddy, Here I am using SQL 2000 and log size of database is max 3 GB that's all no expantion due to bulk-logged recovery mode.
November 13, 2008 at 7:01 am
In fact, I like rebuildm utility of SQL Server 2000 which save time & very quick instead of Setup.exe in SQL Server 2005.
November 13, 2008 at 6:17 am
Has anybody having idea which space SQL Server is USING?
During Maintenance DB is in Bulk-Logged mode.
Here is scenario:
TOTAL DB SIZE: 24 GB
Space Available: 12 GB
Data File: 21 GB
Log File: 3...
November 13, 2008 at 5:53 am
I doubt just changing location of TempDB is acting like this. There must be something beyond this or we are missiong something.
Have you checked DBCC OPENTRAN ? What is the...
November 13, 2008 at 5:30 am
If performance is affected will you kill?
Irespective of performance; you can't kill system processes you will get messge "Only user processes can be killed."
JUST DO NOT WORRY ABOUT THIS PROCESSES.
November 13, 2008 at 5:26 am
Try to findout more detail about the processes running on the Tempdb. Find out any open transactions are there or not in Tempdb?
November 13, 2008 at 5:20 am
Viewing 15 posts - 1,036 through 1,050 (of 1,179 total)