Thanks for your response.  I've tried connecting in Query Analyser also, and get the same error message.  The user i am trying to connect as, is one...

Hi,

i've just been reading a very interesting article on this site called 'The case for SQL Logins'. it might help you out or help you make sense of...

Hi, I'm doing it through enterprise manager, clicking 'all tasks', 'export data'. thanks...

Sorry to bring this up again....still cant figure out why its happening. Has anyone come across this problem before? Any ideas would be great. Its a real...

Thanks for your help.

I changed the DECLARE @year int

to DECLARE @year varchar(4)

and its working now.

another question that i am...

Yeh,they've been there since the server started up. Should I kill them or would that cause a problem?

Any idea why i never see them on my other servers?

Cheers!

Ignore me, I found a check box on the options page that said to force restore over an existing database.

Cheers anyway.

Meg

Hi again,

Please can someone explain why when 'select into/bulkcopy' is set to true, you cant do a transaction log backup.

Also, why does it fix the problem if you do a...

Thanks for the advise guys.

I have found the reason for the logging...there is something set up for checking particular logins. Its needed for that. So i'll...

Hi, thanks for all the advise,

This is a server which part of our company will not let us administer...hence the mess of it!! They only come to me when...

I'm having a problem too with my transaction log backup. it fails all the time.... any ideas of how to fix this (its SQL 7.0)?

Here is the error...

[1] Database standard:...

This is prefect, thankyou!

Also, our company is planning on upgrading to Exchange 2003 Server for the Mail client and upgrading all desktops to XP and servers to Server 2003. ...

Thanks for all your help with this one. I finally got it working. I logged on as the same account running SQL Service directly on the server. Created...

Thanks Guys! Manually it is then....

Meg

I've had this before and it was because we were having problems with the msdb database. Ours was marked as 'suspect'. Is yours?