Viewing 10 posts - 346 through 355 (of 355 total)
looks like the fix in http://support.microsoft.com/kb/955726 solved my problem. The scheduled task completed successfully last night. Thanks for that additional post. Where did that come from?
August 19, 2009 at 10:01 am
do what you can to verify the network connection...maybe try to telnet to that port.
You can also try to setup that with the IP address vs. the hostname.
if you ping...
August 19, 2009 at 9:45 am
This may be part of the issue, If you run SQL Server under a non-domain account, you must use certificates
I'd say start over
Drop everything, and attempt to configure with this...
August 18, 2009 at 9:52 am
This is pseudocode, but you could do something like this...if sp_MSForEachDB works in mode 65
BEGIN
CREATE TABLE #INDEXFRAGINFO
--Create table structure based on result fields
DECLARE @command VARCHAR(128)
SELECT @command = 'Use ['...
June 16, 2009 at 11:03 am
the compatibility level all databases must be 90
June 16, 2009 at 8:11 am
I rebuilt this machine and am getting the error again. Everything is installing except workstation components. The kicker is that I used the same media on a differant...
January 12, 2009 at 4:22 pm
I uninstalled the native client today an then ran the workstation componets installer from the cd. This reinstalled native componenets and then raised the same error again when it...
January 8, 2009 at 10:21 am
thanks noeld, that certainly was the easier way to do it!
So, SQL 2000, are we stuck with using the trace files?
December 31, 2008 at 12:19 pm
At this point it looks like I'm back to my original plan of action. I'll repost my questions, please refer to the first post:
Is there a better way to...
December 31, 2008 at 8:26 am
Thanks for the hint. I've re-written like so:
SELECT TOP 100 [OBJECT_NAME] = OBJECT_NAME((SELECT [OBJECTID]
...
December 30, 2008 at 2:20 pm
Viewing 10 posts - 346 through 355 (of 355 total)