Viewing 7 posts - 226 through 233 (of 233 total)
Yes! partitioning is the best solution if you are using SQL 2005/08. If not, then I need the definition of your table to provide you with an alternative.
-Vikas Bindra
-Vikas Bindra
January 7, 2009 at 4:28 am
Seems like a security issue. Even if you restart the job you will get the same error.
Check this link you will find the solution
http://msdn.microsoft.com/en-us/library/ms151761(SQL.90).aspx
- Vikas Bindra
Sr. Software Engineer - BI
-Vikas Bindra
January 7, 2009 at 4:17 am
As you said that when you execute the package both the groups starts running in parallel, and this is what causing the error. You need to add a "precedence constaint"...
-Vikas Bindra
January 7, 2009 at 3:50 am
Check the credentials under which the SQL Server Agent is running. Also, check in the job properties that you have specified SQL server Agent credentails to be used to execute...
-Vikas Bindra
January 6, 2009 at 1:16 am
You can do it with the help of Execute SQL Task. Here is what you need to do:
- Double click on your SQL task.
- On the general tab set QueryIsStoredProcedure...
-Vikas Bindra
January 6, 2009 at 12:53 am
You need to do the following:
- Save the name of the new file in a variable (@myNewFile) at the time you are creating it.
- Open the Expressions of your Flat...
-Vikas Bindra
January 6, 2009 at 12:31 am
Viewing 7 posts - 226 through 233 (of 233 total)