Viewing 15 posts - 1 through 15 (of 16 total)
I believe this is possible in SQL 2012!
October 14, 2011 at 4:43 am
It can only be a permission issue.
xp_cmdshell uses the SQL Server Service Account.
Ensure this account has write access to the drive your writing too.
October 14, 2011 at 4:42 am
As your attaching across servers there should be no problem with your loop (while or cursor) Id lean towards cursor but that my preference!
🙂
October 4, 2011 at 6:58 am
All Transactions are logged in the transaction log,
when you mirror servers everything from the transaction log get "replayed" on the mirror server.
when you stopped the mirror all the transactions would...
September 23, 2011 at 5:34 am
Try adding this before you rebuild your index. (script out the index from the view and use these set options!)
SET ARITHABORT ON
GO
SET CONCAT_NULL_YIELDS_NULL ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
SET ANSI_PADDING ON
GO
SET...
September 23, 2011 at 3:04 am
Great thread.
As its an issue with stats and the optimiser choosing a different plan would adding
OPTION(RECOMPILE)
not help?
We have had similar issues (but not on the same scale i...
September 23, 2011 at 2:55 am
It will rollback when the database starts up, check the SQL Server Log and there will be a message showing transaction rollback.
July 21, 2011 at 7:11 am
If you populate your historic table with:-
select cast(cast(getdate() as CHAR(11)) as datetime) as RunDate,
columlist etc
This will give you the current date. then the next time you populate your historic table...
July 21, 2011 at 4:48 am
As far as im aware you cant break it down into a per day basis.
If you run your script each day then store the results you will be able to...
July 21, 2011 at 3:59 am
The maximum width of a table is 8060 bytes on SQL 2005 (for In Row Data) . You need to reduce the amount of columns in your table.
July 21, 2011 at 3:49 am
Hi James
You can get some information from Activity Monitor within SQL 2008.
As for 3rd party tools we use SQL Sentry. We did test a few at the time.
This monitors CPU,...
July 21, 2011 at 3:01 am
Or for SQL 2000
To put the DB in emergency mode in 2000, you need to hack the sysdatabases table so the status field has the 'bypass recovery' bit set....
July 8, 2009 at 6:54 am
try setting the database as EMERGENCY:-
ALTER DATABASE dbname SET EMERGENCY
then see if you can run CHECKDB
July 8, 2009 at 6:47 am
Viewing 15 posts - 1 through 15 (of 16 total)