I have a stored procedure with parameters in SQL Server 2000 database. When
I execute it in Enterprise Manager, it takes less than 1 second to return
rows.
When I use it in VB 6 code to populate ADODB.Recordset, it takes more than
30 seconds on this particular line:
Set rsOrders = cndTemp.Execute
I'm wondering why it is like that, and how can I make it work with the same
or at least similar speed in VB?
Re: Execute Persmission denied on object sp_OACreate ... > SQL Server is creating a job behind the scenes. ... > permissions.... > SA account password and gaining access to the database.... >>> How can get a user permissions to execute these stored procedures ... (microsoft.public.sqlserver.security)
RE: xp_cmdshell, ownership chaining, sql 2000 ...Cross database ownership chaining enabled... The procedure is called by a crystal report.... If I log in to SQL Server through SSMS 2005 using the same user as the ... I get the following error when attempting to execute... (microsoft.public.sqlserver.programming)
xp_cmdshell, ownership chaining, sql 2000 ...Cross database ownership chaining enabled... The procedure is called by a crystal report.... If I log in to SQL Server through SSMS 2005 using the same user as the ... I get the following error when attempting to execute... (microsoft.public.sqlserver.programming)
Re: Data migration questions? ... Use SSIS or the SqlBulkCopy class to import the data into SQL Server.... Anyone who has read my books knows that I'm not in favor of including BLOBs in the database...."Mervin Williams" wrote in message ... should I use a DataSet to bring the data down to the local machine that will run the code and execute the transformation logic from it. ... (microsoft.public.dotnet.framework.adonet)
Re: Viewing default db role permissions ... > whether that user or role has access to various objects in the database... > the database in Enterprise Manager, going to the "Role" tree item, ... > checkmarks representing what the role/user has access to and red X's ... > permissions of each of these roles from the SQL Server documentation,... (microsoft.public.sqlserver.security)
