Agreed, but sometimes it's useful, eg including a literal string in a constructed OPENQUERY(), eg :

SET @strCommand = "SELECT * FROM OPENQUERY(server, SELECT * FROM Database.dbo.Client WHERE Surname = '"...

Most SQL errors lead to at least a batch abort so internal error handling is unhelpful. Assuming that you are connecting through ADO, you need to check the ADO...

SET QUOTED_IDENTIFIER OFF allows you to use double quotes as well as single for strings but this is not usually a database default so needs to be included in your...

Is this a SQL error message (it sounds too helpful!) or something from the code? It could be permissions with the access denial misinterpreted - look at sp_AddLinkedSrvLogin.

Can you throw away the view and just access the underlying tables directly?

Easy when you know how! Many thanks.

My VB6 application connecting through ADO puts 'Visual Basic' in the Program Name column. Can anyone suggest as to how to make this more informative?

Because you are converting from a date expressed as text which can be interpreted ambiguously, you still need SET DATEFORMAT YMD or whatever.

Glad I could help.

You might look at Tools/Options/Connection in Query Analyzer. Is is using Regional Settings?

Microsoft defaults assume that everyone is American. That can cause problems if you...

You appear to be missing the third (Style) parameter from CONVERT. Also, consider using SET DATEFORMAT rather than relying on the server default. As a general rule, I...

Double congratulations!

I try at least to respond to as many questions as I ask but you are out of sight! This site is an invaluable resource, in no small...

Perhaps this is oversimplistic - but I like simple - and it avoids triggers which I don't like for performance and because, as a developer, it makes debugging harder /...

The fill factor only applies when the index is created. As inserts occur, this 'spare' space will get filled up until SQL Server is forced to make a page...

If data is added only to the end, then there won't be a page splitting / fragmentation issue (and you can have a 100% fill factor) but is the index...

To add an explanation : SQL Server only returns the last output to ADO. With NOCOUNT off, this is the 'records affected' message and not the recordset (which was...