Is it possible to call an extended stored procedure in SQL Server 2005?
Hi, I believe that you have some minor problems with the SQL server. Just from my own experience, I can recommend an excellent blog about ddl commands in sql) where the main points of troubles when working with sql are described. Considering that I have more than 5 years of development experience, but I still face such problems and this blog helps me solve them.
I’m having a problem calling an extended stored procedure (specifically xp_cmdshell) from java, using the JDBC for SQL Server 2005. By using the JDBC for SQL Server 2000 Service Pack 3, I can call it like a normal stored procedure. With SQL Server 2005, I get the following: om.microsoft.sqlserver.jdbc.SQLServerException: The request for procedure ‘xp_cmdshell’ failed because ‘xp_cmdshell’ is a procedure object. It is a SQL Server 2000 server. I want to use the new 2005 JDBC because it does not have problems with cloned connections in manual transaction mode. I had problems with the selectMethod=cursor property on my webserver, it just didn’t seem to take. It worked fine from my local webserver during development, but for some reason doesn’t work when running on the live webserver. Is it even possible to call this extended stored procedure? Yes, by default, it’s disabled in 2k5 as it’s not considered safe. You can enable it using the Surface Area Configuration Tool if you think it’s app
- When I create or edit a stored procedure or trigger through SQL Server Enterprise Manager, pressing the TAB key changes the context to each button. How can I indent my Transact-SQL statements?
- Is it possible to call a stored procedure with parameters using ADO.NET?
- Is it possible to call an extended stored procedure in SQL Server 2005?