Viewing 15 posts - 301 through 315 (of 405 total)
Thanks Ian. You are correct, I needed only full backups. I have included that in my query.
September 3, 2009 at 7:22 am
http://support.microsoft.com/kb/271509
http://www.sqlservercentral.com/articles/Performance+Tuning/67134/
August 26, 2009 at 11:38 pm
Any error do you get when you try to connect?
August 26, 2009 at 7:08 am
Do you have this problem in query analyzer?
I if understood your problem correctly its limitation in output display only.
You might want to change the default setting in
tools> options>results>maximum characters...
August 26, 2009 at 6:54 am
select * from sysperfinfo where counter_name like '%page life expectancy%'
A generalization is that if it is above 300, it is unlikely that you have memory pressure
Edit: use master
August 26, 2009 at 5:59 am
if apply David Burrows's suggestion in the Dave's code it would be
select * from #t1 where ','+ValueStr+',' like '%,2,%'
no?
August 24, 2009 at 6:09 am
Thanks Grant. I got the point. I was asked how to place files for a new project and I actually did suggest that the safest bet was three different drives...
August 19, 2009 at 7:06 am
Grant Fritchey (8/19/2009)
August 19, 2009 at 5:43 am
Of course we are getting professional help in this matter, meanwhile I was trying to gather some information. I could not find much over the internet. Anyways thanx.
August 18, 2009 at 3:32 am
Adam,
I have three instances in active / passive cluster setup.
The current version is as follows
...
August 13, 2009 at 2:28 am
Thank you all.
@ Adam : Yes the I was refering to sql service when i said active/ passive. Now all instances in one node is patched and the second is...
August 13, 2009 at 12:25 am
Mayur,
Don't know whether there is a table for this. However you can get this info using trace. Please see the below blog
August 6, 2009 at 1:23 am
Where do you check the version?
Did you upgrade all components? Database Engine, Tools etc
in Query window if you type select @@version, what is the output
July 10, 2009 at 4:12 am
Seems you have corruption on your index. id 0 suggests that you might loose some data if you repair. Did you try running checkDb?
July 8, 2009 at 7:40 am
Sorry I did not notice that it was 2000
Please check whether the following link helps you
http://www.gerixsoft.com/blog/mssql/recovering-mssql-suspect-mode-emergency-mode-error-1813
July 8, 2009 at 6:36 am
Viewing 15 posts - 301 through 315 (of 405 total)