Viewing 15 posts - 196 through 210 (of 1,363 total)
Try:
On Pri. server
select * from msdb.dbo.log_shipping_primary_databases
On Sec. server
select * from msdb.dbo.log_shipping_secondary
February 7, 2010 at 1:16 am
Casper,
Use the column named 'AVERAGE_BYTES_PER_ROW' generated by attached script and multiply it with number of rows that qualifies for deletion for that particular year. It will give you an estimate.
Note:-...
February 5, 2010 at 11:39 am
Try specifying a job log file in that stored procedure execution step which is failing and post the error message from log file here.
MJ
February 5, 2010 at 5:04 am
Example:
CREATE TABLE [dbo].[Statsdate] (
[Statsdate] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
declare @pos int
insert statsdate
EXEC master..xp_cmdshell 'net STATISTICS server | find "Statistics since"'
delete from statsdate where statsdate is null
select @pos=...
February 4, 2010 at 9:24 pm
Better take it in a sql table and format it there.
MJ
February 4, 2010 at 2:34 pm
Run 'sp_helpuser' under SSMS and see if that windows group actually got that role assignment or not.
MJ
February 4, 2010 at 12:55 pm
What message do u get in SSMS once you run tht t-sql statement?
Manu
February 4, 2010 at 12:40 pm
Your script returns incorrect time when job executes before noon time.
Use this:
SELECT jobs.name as 'JOB_NAME',his.message as 'MESSAGE',
ISNULL(SUBSTRING(CONVERT(varchar(8),his.run_date),7,2) + '/'
...
February 3, 2010 at 1:51 pm
February 2, 2010 at 6:05 am
We had the same error message with our Server. One thing that I remember from it that it will work if you are using a SQL login but if you...
February 2, 2010 at 5:51 am
Try:
http://www.ureader.com/msg/1161666.aspx
To resolve this problem:
1. I changed Log On information of MSSQLServer from Windows Services.
2. I also changed Log On information of SQLServerAgent from Windows
Services.
To do 1 & 2 go to...
February 2, 2010 at 5:11 am
February 2, 2010 at 5:04 am
Try scheduling it as a job and see it it creates file.
MJ
February 2, 2010 at 4:56 am
Simply run the SQL installer again and create a new clustered SQL Instance. Note that the new instance will also need a new, unique IP address and a network name...
February 2, 2010 at 4:46 am
Viewing 15 posts - 196 through 210 (of 1,363 total)