That's a bad idea.
If we ignore that you don't define either of the stored procedure parameters you are using (and that means it won't work at all anyway), the problem is that that code relies on your SQL Server instance having both the actual image files stored on it, and that the SQL Server process has access to the folders containing them.
In production, neither of those is likely to be true: the SQL Server instance is likely to be a separate machine (or farm of machines) to which users have no direct access for security reasons, and for similar reasons, the server process will be restricted to only those folders it needs to do it's job, such as the DB storage directory.
A much better idea is to pass the image data as a parameter instead of the path from your presentation software when you call the stored procedure. That's easy to do in most languages, this shows how to do it in C#: Why do I get a "Parameter is not valid." exception when I read an image from my database?