Don't ever create or alter procs in Enterprise Manager. Use Query Analyzer and specify SET QUOTED_IDENTIFIER and ANS_NULLS ON or OFF as
required. Prefereably always ON.
Your code fragment looks wrong anyway. Presumably it should be:
SELECT @SQL1 = 'SELECT @Total1 = Count(*) FROM dbo.Tbl_Report WHERE
Utilisateur = '''+@utilisateur+''''
Linked Server Problem ... I have a view to a table in a linked server (an Access mdb... file) that works fine in Enterprise Manager and Query...Analyzer, but when the view is executed in the Access adp ... (microsoft.public.access.adp.sqlserver)
Re: Tools with/for Express ... Enterprise Manager does not work with SQL Server 2005. ...Analyzer is pretty dumb and just passes on what you type, ... But Enterprise Manager tries to write it's own code and it doesn't use SQL ... I then attempted to use Query Analyzer.... (microsoft.public.sqlserver.tools)
Re: ODBC error: [Microsoft][ODBC SQL Server Driver]Invalid cursor ... My first suggestion is that you really should be using Query...Analyzer for those types of activities. ... >using Enterprise manager and when changing colum name I get this error. ... >>>I am trying to rename a column name and it gives me the following error. ... (microsoft.public.sqlserver.odbc)
RE: Enterprise Manager Shortcuts for Remote Servers ... I don't think I have a restriction for Query... Does this mean I'd have to switch to Query Analyzer or are you suggesting ... that back to using Enterprise Manager?... doesn't allow you to store a default database for each SQL Server ... (microsoft.public.sqlserver.server)
Re: Source control integration with MSSQL 2000. ... I tested sqlXpress about a year or so ago. ...query plans, which was something I couldn't do without. ... > using both Query Analyzer and Enterprise Manager.... > - Their website says "Replaces most features of Microsoft® Query Analyser ... (microsoft.public.sqlserver.server)
