Viewing 15 posts - 91 through 105 (of 116 total)
Type msinfo32 in start-->run mode , takes you to the system information.Check for the system type, processor..if they are X86 based then it is a 32 bit else 64 bit.
Properties...
July 21, 2009 at 5:20 pm
Did u try something like this:
use master
backup database ...
I have never tried though
July 21, 2009 at 12:43 pm
Hope it shud hold them, but can do a simple try checking the .trn backup file size after inserting only images and backing it in a sample db.
July 21, 2009 at 12:41 pm
How about trying to execute the job with t-sql using if/else or case statements.Just a guess.
July 21, 2009 at 11:02 am
Just a blind guess
Has the rebuild index job ran with a change in the fill factor from 5-10% or something like that.
July 21, 2009 at 10:33 am
Is this the first time you are logging?
if IIS is fine:
looks like you need to review ssrs configuration:
Reporting Services Configuration Tool
http://msdn.microsoft.com/en-us/library/ms156305(SQL.90).aspx
also
Troubleshooting Reporting Services
http://msdn.microsoft.com/en-us/library/ms159135(SQL.90).aspx
may be try this:
Change...
July 21, 2009 at 10:29 am
Is the 90GB growth on mdf or ldf or is it combined?
Check for the space usage of all the tables, check for reserved space here.
July 21, 2009 at 10:19 am
I havent seen it documented anywhere, but I had it in my experience many times.
Autogrowth value going to 6-7digit as percentage!!!
July 21, 2009 at 10:14 am
there is also a bug in SQL 2005 with autogrowth when you restore a db or restart the services etc.
In the view sys.database_files is_growth_percent changes from 0-1, which means that...
July 21, 2009 at 10:00 am
There can be many reasons like
network glitch at that time, someone amended the pwd's, services restart etc.
July 21, 2009 at 9:55 am
Is this the first time you are logging to SSRS?
Check if you have already configured reporting services at
All programs-->SQL 2005-->Conf. tools-->reporting services conf.
You should see all ticks there.
July 21, 2009 at 9:52 am
try connecting to them using SQL authentication mode instead of windows authentication with a valid credentials.
July 21, 2009 at 9:48 am
Looks like a connection failure, check if the users credentials who run the job are still the same or changed?.
Try manually executing the job with some valid connections and let...
July 21, 2009 at 9:43 am
Viewing 15 posts - 91 through 105 (of 116 total)