What do you mean by collation recursive stored procedure?
- 1 Answers
- 1142 Views
- I also Faced
- E-Mail Answers
Answer Posted / Amar Pal Singh
A collation recursive stored procedure is a stored procedure that uses the RECURSIVE WITH UNION keyword to execute itself repeatedly while meeting certain conditions. Collation determines how SQL Server compares character data, and a collation recursive stored procedure can be used for iterative tasks such as traversing hierarchical data or performing deep recursion.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What is sql server query analyzer?
What are different types of constraints?
Can we do dml on views?
What are the risks of storing a hibernate-managed object in a cache? How do you overcome the problems?
Can you index views?
How do I start sql server 2017?
What are wait types?
How to remove duplicate rows from table except one?
Where can you add custom error messages to sql server?
How to rebuild the master database?
What is normalization and what are the advantages of it?
How to convert character strings into numeric values?
If any stored procedure is encrypted, then can we see its definition in activity monitor?
This question asked during interview, 2) At the end of each month, a new table is created for each bank that contains monthly metrics consolidated at the account level. The table naming convention is bankX_YYYYMM where X represents the numeric designation of the bank and YYYYMM indicates the 4 digit year and 2 digit month. The tables contain the following fields: name data type description account text account number registered boolean indicates whether the account is registered num_trans integer number of transactions made during the time period spend numeric(9,2) total spend during the time period a) Write a SQL query that will display the total number of transactions and total spend for "Bank1" during the 4th quarter of 2009. b) Write a SQL query that will display the total number of transactions and total spend at "Bank1" and "Bank2", broken out by registered vs. non-registered accounts, during January 2010 not sure what is correct answer and how to solve?
Can we shrink data file in sql server?
