Thanks to all you guys for every bit of help....

Finally found out what the exact problem was... The auditors needed the public permission on msdb.dbo.sp_get_dtspackage to be revoked to protect...

Vishal,

What I meant by Non-privileged users was users other than sysadmin users(DBA's)... Ofcourse the Non-privileged users have access to SQL Server...

Sorry if I was not clear on that... 🙂

Now as...

Security audit was done by a third party... I believe they used some tools for this purpose... In their final output to the management they gave this point that in...

Does it occur only at your end or did you try connecting to the server from any other machine ??

Does it give you any error when you connect to a server from Object Explorer ??

Hey thanx a lot... Exactly wot I was looking for...:-)

Hey thanks a lot man.. Just figured it out... The compatibility level had been set to SQL Server 7.0(70)...

From what I can understand you need to know more about your database structure... Basically a better understanding of the database... Try out some third party tools... I'll suggest Dezign......

Data file has an autogrowth set by 1 MB (Unrestricted) and the Log file has an unrestricted autogrowth of 10 Percent...

The whole database size is 75Gb... The Database recovery model is set to SIMPLE and as expected the log file size is very less... It's around 1Gb... The data file...

Try this for a start to set up Transactional Replication

http://www.informit.com/articles/article.aspx?p=599700

Also try out this webcast

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032263302

SQL Server does not allow browsing drives on other servers(for Backup and Restore) while using Management studio. You will have to copy the backup from the remote machine to your...

First of all try pinging your Server from the client machine...

If that succeeds then make sure your remote connections are enabled from Surface Area Configuration...

Double check and make...

Check your errorlogs to know more about the kind of error you are getting. It can be an error related to your SQL Server or it can be something outside...

Thanx a lot guys....