November 28, 2018 at 9:42 pm
Comments posted to this topic are about the item Short Variables
November 29, 2018 at 11:21 am
Steve Jones - SSC Editor - Wednesday, November 28, 2018 9:42 PMComments posted to this topic are about the item Short Variables
Thanks for this question Steve. It is clear that the shortest write is @ but I chose answer # 4, because the sysname data type is used for variables.
See DOCS in Database Identifiers, or the sysname paragraph in Using Special Data Types and Remarks in nchar and nvarchar (Transact-SQL).
You can verify information about SYSNAME with:EXEC sp_help SYSNAME;
GO
November 29, 2018 at 11:28 am
Not sure where sysname comes in here with "all variables", but am I missing something?
November 29, 2018 at 11:42 am
I'm sorry, I mistaken it with the space needed for the names of the variables...:crazy:
November 29, 2018 at 3:58 pm
My Google-fu is failing me but I thought I had read that using @ or @@ alone had been deprecated by Microsoft.
November 29, 2018 at 4:38 pm
Haven't seen anything on that. It's not on the @(local variable) page that I see.
Then again, I don't think it's a good idea. Just an interesting question
November 29, 2018 at 10:11 pm
bah, this bit me.. I also thought i read that the use of @ or @@ was deprecated, but cannot remember where.
Really interesting question, thanks Steve
IMHO, to do that, though, is just an incident waiting to happen - will also make support a nightmare...
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
November 30, 2018 at 12:02 am
Stewart "Arturius" Campbell - Thursday, November 29, 2018 10:11 PMbah, this bit me.. I also thought i read that the use of @ or @@ was deprecated, but cannot remember where.
Really interesting question, thanks Steve
IMHO, to do that, though, is just an incident waiting to happen - will also make support a nightmare...
This got me too, I thought the question referred to the fact that all variables are initialized as null unless a value is provided.
As far as deprecation is concerned Stewart's (and Lynn's) memory serves them well, one such reference is here (under the Transact-SQL section), although arguably this applies from SQL2016.
...
November 30, 2018 at 2:53 am
If they haven't deprecated it then they definitely should!!
November 30, 2018 at 5:53 am
allinadazework - Friday, November 30, 2018 2:53 AMIf they haven't deprecated it then they definitely should!!
According to MS they have!! See the link provided.
...
November 30, 2018 at 6:04 am
Stewart "Arturius" Campbell - Thursday, November 29, 2018 10:11 PMbah, this bit me.. I also thought i read that the use of @ or @@ was deprecated, but cannot remember where.
Really interesting question, thanks Steve
IMHO, to do that, though, is just an incident waiting to happen - will also make support a nightmare...
Hi Stewart
Maybe it could be here: SQL Server, Deprecated Features Object
December 5, 2018 at 9:23 am
Lynn Pettis - Thursday, November 29, 2018 3:58 PMMy Google-fu is failing me but I thought I had read that using @ or @@ alone had been deprecated by Microsoft.
You are correct. Doing this has been deprecated starting with the release of SQL Server 2008. You can find it mentioned on the following archived documentation page for "Deprecated Database Engine Features in SQL Server 2008" under "Features Not Supported in a Future Version of SQL Server". Just do a "find" for "@@". (and in case anyone was wondering, I did check the 2005 documentation and there is no mention of this)
You can also create a local temp table with a name of just "#", or even a global temporary table named "##". Not that you should, but you can. Also deprecated as of SQL Server 2008.
But, even with both being deprecated, I don't see this "ability" being fully removed anytime soon.
For the complete list of rules that govern identifier names (including variables), please see my post:
Completely Complete List of Rules for T-SQL Identifiers
Take care, Solomon..
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR
December 6, 2018 at 12:42 am
George Vobr - Friday, November 30, 2018 6:04 AMStewart "Arturius" Campbell - Thursday, November 29, 2018 10:11 PMbah, this bit me.. I also thought i read that the use of @ or @@ was deprecated, but cannot remember where.
Really interesting question, thanks Steve
IMHO, to do that, though, is just an incident waiting to happen - will also make support a nightmare...Hi Stewart
Maybe it could be here: SQL Server, Deprecated Features Object
That's the one, thanks George.
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
December 6, 2018 at 3:43 am
Solomon Rutzky - Wednesday, December 5, 2018 9:23 AMBut, even with both being deprecated, I don't see this "ability" being fully removed anytime soon.
When a feature is marked deprecated, it means:
- The feature is in maintenance mode only. No new changes will be done, including those related to inter-operability with new features.
- We strive not to remove a deprecated feature from future releases to make upgrades easier. However, under rare situations, we may choose to permanently remove the feature from SQL Server if it limits future innovations.
- For new development work, we do not recommend using deprecated features.
December 6, 2018 at 7:38 am
Toreador - Thursday, December 6, 2018 3:43 AMSolomon Rutzky - Wednesday, December 5, 2018 9:23 AMBut, even with both being deprecated, I don't see this "ability" being fully removed anytime soon.When a feature is marked deprecated, it means:
- The feature is in maintenance mode only. No new changes will be done, including those related to inter-operability with new features.
- We strive not to remove a deprecated feature from future releases to make upgrades easier. However, under rare situations, we may choose to permanently remove the feature from SQL Server if it limits future innovations.
- For new development work, we do not recommend using deprecated features.
Interesting. I guess I was going by the wording on the older pages, such as what was there back on the 2008 page (the one linked in my post above):
(at the top of the page -- emphasis mine)
This topic describes the deprecated SQL Server Database Engine features that are still available in SQL Server 2008. These features are scheduled to be removed in a future release of SQL Server.
(under "Features Not Supported in a Future Version of SQL Server" -- emphasis mine)
The following SQL Server Database Engine features are supported in the next version of SQL Server, but will be removed in a later version. The specific version of SQL Server has not been determined.
Thanks for pointing this out. Take care, Solomon...
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply