Viewing 15 posts - 1,006 through 1,020 (of 3,738 total)
HanShi (6/25/2013)
You've made a type in the restore command. You have missed the ":" after the drive.MOVE 'MyDBDW_log' TO 'E\MSSQL\Log\MyDBDW.ldf'
must be:
MOVE 'MyDBDW_log' TO 'E:\MSSQL\Log\MyDBDW.ldf'
I do not see a difference in...
June 25, 2013 at 4:46 pm
I commented out the Log file and I was able to restore.
That is not necessarily what I want.
I restore quite frequently but not to this Server.
Very strange.
June 25, 2013 at 12:05 am
I got it to work:
RESTORE DATABASE MyDBStaging
FROM DISK = 'I:\Backups\CYP_DW\Full\MyDBDW\MyDBDW_backup_2013_06_24_163430_3276765.bak'
--WITH RECOVERY
WITH MOVE 'MyDBStaging' TO 'E:\MSSQL\Data\MyDBStaging.mdf',
MOVE 'MyDBStaging_log' TO 'E:\MSSQL\Log\MyDBStaging.ldf',
REPLACE
June 24, 2013 at 6:45 pm
ok, sorry everyone.
It has ben a long day.
I have a bunch of other fisk to fry, sorry to cut corners.
Regards.
June 24, 2013 at 6:14 pm
I get the error the Database is not accessible for a user.
What is wrong?
I can't find an answer.
June 24, 2013 at 2:21 pm
Thanks for the help guys.
I'm using the Data calculation in the WHERE Clause.
WHERE Effective_Date < CONVERT(DATE, DateAdd(yy, - 5, GetDate()));
Does it matter which method I use as far as performance?
June 24, 2013 at 10:38 am
I'm using the Derived Date in the WHERE Clause.
WHERE Effective_Date <
June 24, 2013 at 10:36 am
Hey, thank you very much!
June 23, 2013 at 3:03 pm
I had someone perform an SELECT INTO and let it run for a day and it caused tempdb to grow to 800 GB.
So I tried shrinking the file with the...
May 22, 2013 at 6:23 am
jpSQLDude (5/21/2013)
But I can run ad-hoc queries. So the sp_who3 that is here I can run just by removing the CREATE PROCEDURE bits http://sqlserverplanet.com/dba/a-better-sp_who2-using-dmvs-sp_who3. Unfortunatley running that variation...
May 21, 2013 at 4:12 pm
It sounds to me as if the OP does not have the required permissions to do a lot of things.
That being said they can't use remotely connect to the machine...
May 21, 2013 at 9:01 am
jpSQLDude (5/21/2013)
May 21, 2013 at 7:15 am
kevaburg (5/21/2013)
How about checking the Windows Task Manager first to make sure that it really is SQL Server using up the processor time.
If you look above the OP already did...
May 21, 2013 at 6:13 am
If you are not a member of the Fixed Server Role sysadmin then you will not be able to view the active SPIDS.
May 20, 2013 at 2:50 pm
The following is fine:
http://sqlserverplanet.com/dba/a-better-sp_who2-using-dmvs-sp_who3
I execute it several times per day and if I want to capture the entire SQL Statement I execute sp_WhoIsActive.
Pick one and try it out.
May 20, 2013 at 1:14 pm
Viewing 15 posts - 1,006 through 1,020 (of 3,738 total)