Google is your friend, but on a slightly more helpful note, there are a whole heap of distinctions and IMO and experience one is definitely not interchangeable for the other.
In a very brief summary:
BA - document the business requirements, i.e. what business benefit(s) the user wants the project to deliver.
SA - document how the system will function and what functionality, rules, system resources etc. will be required to deliver the business benefits as described by the BA.
In reality what usually happens is a "BA" is asked to fulfil all of their role and part of the SA role, subsequently the developers are asked to fulfil the residual part of the SA's role.