February 9, 2019 at 5:49 am
Looking for alternatives in SQ server for the below 3 options (currently these been performed by using Oracle), So same how can I do the in SQL directly or by using any other tools.
1)DBMS_Application (Tracing option in Oracle)
2)DBMS_Session (Used in Oracle):
3)how we can disable or enable DBMS_Output at database level?
Thanks in Advance
February 9, 2019 at 11:10 am
DuploDupl post, ignore.
...
February 10, 2019 at 1:58 pm
pawan.mantha - Saturday, February 9, 2019 5:49 AMLooking for alternatives in SQ server for the below 3 options (currently these been performed by using Oracle), So same how can I do the in SQL directly or by using any other tools.
1)DBMS_Application (Tracing option in Oracle)
2)DBMS_Session (Used in Oracle):
3)how we can disable or enable DBMS_Output at database level?Thanks in Advance
Sorry...both your threads have been marked as duplicates so I guess we should try to answer one of them 🙂
SQL Server has pretty extensive tracing options with extended events. And some of the DMVs provide the information that you would get from DBMS_Application.
For DBMS_Session, it depends on how you are using the package, which functions. If you are using to store session information, session_context is similar. The others, which I don't remember all or much of them, some can be done by querying different DMVs.
There is no dbms_output so you can't enable or disable it at the database level. For debugging, some of the same information can be captured with print statements or checking some of the dmvs for the session.
I think for all of these there is no direct 1:1 type of equivalents. You just do things differently in Oracle and SQL Server. If this is for a migration to SQL Server, you would probably want to look at the functionality you want to replace rather than finding the same packages. SQL Server doesn't have packages and Oracle packages have different subprograms. They are just not the same. So focus on what it is you are trying to accomplish rather than what the package is - especially when those have subprograms.
Sue
February 10, 2019 at 9:19 pm
Sue_H - Sunday, February 10, 2019 1:58 PMpawan.mantha - Saturday, February 9, 2019 5:49 AMLooking for alternatives in SQ server for the below 3 options (currently these been performed by using Oracle), So same how can I do the in SQL directly or by using any other tools.
1)DBMS_Application (Tracing option in Oracle)
2)DBMS_Session (Used in Oracle):
3)how we can disable or enable DBMS_Output at database level?Thanks in Advance
Sorry...both your threads have been marked as duplicates so I guess we should try to answer one of them 🙂
SQL Server has pretty extensive tracing options with extended events. And some of the DMVs provide the information that you would get from DBMS_Application.
For DBMS_Session, it depends on how you are using the package, which functions. If you are using to store session information, session_context is similar. The others, which I don't remember all or much of them, some can be done by querying different DMVs.
There is no dbms_output so you can't enable or disable it at the database level. For debugging, some of the same information can be captured with print statements or checking some of the dmvs for the session.
I think for all of these there is no direct 1:1 type of equivalents. You just do things differently in Oracle and SQL Server. If this is for a migration to SQL Server, you would probably want to look at the functionality you want to replace rather than finding the same packages. SQL Server doesn't have packages and Oracle packages have different subprograms. They are just not the same. So focus on what it is you are trying to accomplish rather than what the package is - especially when those have subprograms.Sue
Thanks Sue for the response I have posted my query in sql administration / development because i am sure in which category it falls
I will see try the solution which u mentioned
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply