Viewing 15 posts - 136 through 150 (of 225 total)
What build version of SQL 2005 are you currently on?
You said...
This cleanup is not working in 2 maintenance plans
So does this mean other cleanup tasks are working? ...
September 2, 2008 at 6:10 am
No, I'm not in the UK. I did figure out the problem, though. Turns out I'm a bit of an idiot... I needed SQL_LATIN1_GENERAL_CP1_CI_AS after all. :ermm:
Nevermind...
September 1, 2008 at 8:16 am
I guess this very much depends upon the criticality of the databases hosted. As for us well we get downtime once a month for MS patching etc. So...
September 1, 2008 at 5:57 am
Try using a search engine or BOL. There are many hits for this sp.
August 29, 2008 at 8:09 am
http://www.sqlservercentral.com/articles/Administration/2987/
Just seen your last post... good article though!
August 29, 2008 at 5:45 am
The Microsoft site should provide feature comparisons etc http://www.microsoft.com/sql
August 28, 2008 at 8:42 am
As a matter of interest are you based in the UK? What are the regional settings of your SQL 2005 Server? You mentioned it's a collation issue... what...
August 28, 2008 at 7:39 am
Hi,
Are you using SQL or Windows collations settings? It seems from your post that you are using windows collation settings which are dependent upon your windows locale. See...
August 28, 2008 at 6:31 am
See http://www.microsoft.com/sql/howtobuy/licensing.mspx for Microsoft licensing options. What's the reasoning behind Standard Edition?
Also see http://www.microsoft.com/sql/editions/default.mspx for feature comparisons between SQL editions.
August 20, 2008 at 6:24 am
August 20, 2008 at 6:11 am
We sure have Jack... lol. At least everything's resolved now Steven.
By running telnet sqlservername 1433 from a cmd prompt this will establish whether you are able to connect to...
August 15, 2008 at 8:00 am
I agree with Jack you should not need to enable 'remote connections' even if you intend to connect using SSMS from your own desktop. Although this may depend upon...
August 15, 2008 at 7:11 am
Try logging in using SQLCMD, so from a command prompt window type the following command
sqlcmd -S ANTEC2SERVER\SQL2005 -E
-S server
-E trusted connection
quit to exit
August 15, 2008 at 6:59 am
Hi Stephen,
So what do you actually see when you try and connect using SSMS? Are you trying to connect to default or named instance of SQL?
Also, where are you...
August 15, 2008 at 6:09 am
Hi Jeroen,
I think I just copied distmdl.mdf & distmdl.ldf from another server/instance that had not been upgraded back to the server I was trying to upgrade.
Regards,
Mark
August 15, 2008 at 3:22 am
Viewing 15 posts - 136 through 150 (of 225 total)