Viewing 15 posts - 5,086 through 5,100 (of 7,187 total)
Somehow the Lookup override in SSIS is throwing things off. Maybe the Lookup SQL Override takes parameters differently.
That's the point I was trying to make, Joice - that SSIS and...
September 7, 2011 at 6:47 am
If you use your favourite internet search engine to look for that error message, high up on the list should be a Microsoft support page that gives lots of information...
September 7, 2011 at 4:09 am
Joice
I don't know what the problem is, then. The only thing I can think of is to set something up that writes the values of the parameters to a...
September 7, 2011 at 1:58 am
Joice
Do you know what values are being passed to the CHARINDEX expressions? If they're numbers in character format, they might be getting interpreted as integers when the database engine...
September 6, 2011 at 8:47 am
Let us know how you get on, Brandie. You can make the toolbox auto hide again once it is docked where you want it.
John
September 6, 2011 at 5:51 am
Brandie
Floating might be unavailable because the toolbos is Auto Hide. If you turn that off, you should be able to drag the toolbox and dock it at the bottom...
September 6, 2011 at 5:46 am
You could try logging the output of your job to a table instead of to a file. Then you can query the table, remove rows that you don't need,...
September 6, 2011 at 4:42 am
As I said, I've never tried it myself, so it's up to you to experiment. Start with the events in the Security Audit section.
John
September 5, 2011 at 6:59 am
In that case, it'll be the database name specified in the connection string passed by the application. You have the IP address of the computer the connection was made...
September 5, 2011 at 6:44 am
Try using the PRINT command to see what SQL you will be executing. It might be obvious what the problem is if you do that. In the absence...
September 5, 2011 at 6:37 am
Zohreh
You need third-party software to do this. Search for "sql log reader software". It's not cheap!
John
September 5, 2011 at 3:58 am
I see what the issue is here, but I havn't got time to give it much consideration at the moment. The issue is that you have the same person...
September 1, 2011 at 8:23 am
Something like this?
SELECT
ID,
COALESCE(Field1-Field1+1,0)+COALESCE(Field2-Field2+1,0)+COALESCE(Field3-Field3+1,0)+COALESCE(Field4-Field4+1,0)
FROM
(
SELECT 'A' AS ID,1 AS Field1,2 AS Field2,3 AS Field3,4 AS Field4 UNION
SELECT 'B' AS ID,NULL AS Field1,2 AS Field2,3 AS Field3,NULL AS Field4 UNION
SELECT 'C' AS ID,NULL...
August 31, 2011 at 8:25 am
Pratap
You may find that you can't drop a user if it already owns objects. But there's a good way of finding out - try it, preferably on a test...
August 31, 2011 at 3:33 am
Pratap
Are there any objects named MyUser.ObjectName, where MyUser is the user you want to delete? If so, consider using sp_changeobjectowner.
John
August 31, 2011 at 2:08 am
Viewing 15 posts - 5,086 through 5,100 (of 7,187 total)