Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.
Calling a method from sql server 2008: method static
This method 'GetStringFromNumber' is made of. net and I will use my database sql server 2008
When I declare as follows
public string GetNumberString (double value)
displays the following message
ConvertirNumerosALetra Procedure, Line 1Method, property or the 'GetStringFromNumber'class
So the solution is
public static string GetNumberString (double value)
I want to know why?
When I declare as follows
public string GetNumberString (double value)
displays the following message
ConvertirNumerosALetra Procedure, Line 1Method, property or the 'GetStringFromNumber'class
So the solution is
public static string GetNumberString (double value)
I want to know why?
Asked:
2 Solutions
the "why" is because you (sql server, actually) need(s) to be able to call the method without needing to initiating an object from the class that holds the method.
it's a "by design" issue.
it's a "by design" issue.
The reason for this behavior is that SQL Server doesn't instantiate the class - it just calls into the code. Since nothing is persisted, there's no way to keep a class reference, so the code needs to be static to ensure that. In your case, the method likely acts only on it's parameters, not relying on any state external to itself, so you're fine to just slap a "static" on there without much thought. It's when you're interacting with other objects in your class or others that are shared that you can run into problems with a poorly planned "static" modifier.
Also, since SQL Server is naturally multi-threaded, it need to ensure that multiple threads can call the method at a time without stepping on each other. When you declare the method static, (to me at least) it means you've thought about the implications of that and that you've built your class appropriately, not using any globals, but keeping all the variables internal to your method, where they're safe for multi-threading.
When you think about the context in which SQL Server is consuming your method, it makes sense, but it confused me at first as well.
Also, since SQL Server is naturally multi-threaded, it need to ensure that multiple threads can call the method at a time without stepping on each other. When you declare the method static, (to me at least) it means you've thought about the implications of that and that you've built your class appropriately, not using any globals, but keeping all the variables internal to your method, where they're safe for multi-threading.
When you think about the context in which SQL Server is consuming your method, it makes sense, but it confused me at first as well.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Tackle projects and never again get stuck behind a technical roadblock.
Join Now