Viewing 15 posts - 121 through 135 (of 155 total)
yes. Please install SP2.
March 20, 2008 at 2:40 pm
use dbcc shrinkfile with notruncate and then truncateonly. It will do what you are expecting if there is no open transaction.
March 20, 2008 at 12:45 pm
use
DBCC shrinkfile (filename, expected size in MB , notruncate)
once this is completed then
DBCC shrinkfile(filename, expected size in MB , truncateonly)
This will do trick.
March 20, 2008 at 10:42 am
Which version of SQL Server? If it is 2005 then do you have SP2 installed?
March 20, 2008 at 10:37 am
Please check this http://msdn2.microsoft.com/en-us/library/ms187864.aspx
March 20, 2008 at 10:29 am
Although there is hotfix available for this issue that brings 9.00.3186.00. But My experience says it does not resolve issue completely. Hence, to resolve this issue you have to clear...
March 20, 2008 at 10:26 am
Please check this http://www.sqlservercentral.com/Forums/Topic13928-8-1.aspx
March 19, 2008 at 2:08 pm
If you are storing your file on same machine then there is definetely a process running that locks that file (as stated in earlier post) which leads file not being...
March 19, 2008 at 2:02 pm
March 19, 2008 at 12:47 pm
You can use import wizard to do this that is available under TASKS property of Database.
March 19, 2008 at 12:44 pm
I have it running on 64 bit box and it is doing job without any problem.
March 19, 2008 at 12:42 pm
Alter is good if you want to ensure existing security setting on SP otherwise it does not matter.
March 19, 2008 at 12:36 pm
Do you have any file backup process running for drive where you store your trace file? something like TSM. Such error is expected in that case.
March 19, 2008 at 12:07 pm
Query that performs slow:
select * from Table1
where column4 IS NULL
Sample Data in Table:
1124100065.16
1156101101.11
11781015NULL
118991015NULL
11989102834NULL
March 14, 2008 at 8:57 pm
Viewing 15 posts - 121 through 135 (of 155 total)