Verify that the technical limitation I named actually exists, then find a workaround or an alternative. Better yet, make a list, naming merits and expected problems for each; make prototypes of the best two ideas.
To get you started; you could opt to write a browser-addin (for each type of browser you want to support) that acts as an intermediate, or, you'd write a client-side application (think WinForms/WPF) that provides the same functionality.
The latter will sound like a bad idea to your professor; then again, it would not only be the correct approach; you'd end up with a finger-print protected password-manager. Would not require a dedicated server, as it could run completely (!) on the client. There's no risk in me loosing data, as all my sensitive data never has to leave the client-machine. And best of all, you wouldn't need Google's cooperation to provide the functionality and being able to claim to support GMail.
If you take the latter approach, then you might also want to look up the strategy-pattern. It would be nice if the password-manager also supports other ways of authenticating/authorizing.
That would be targetting a shrinkwrap-application. If your course requires you to write an enterprise-level application, you'd need the first approach.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
and I am looking for the columns available in that temp table for the same session id.
you can refer code below for the same.
(id int , name varchar(450) )
select c.* ,t.name from tempdb.sys.columns c
INNERJOIN tempdb.sys.tables t
on c.object_id = t.object_id
where t.name = '#tmp_table'-- don't use like '%tmp_table%'droptable #tmp_table
Another oddity of the local temporary table (and the local temporary stored procedure) is that it has a different name in the metadata to the one you give it in your routine or batch. If the same routine is executed simultaneously by several processes, the Database Engine needs to be able to distinguish between the identically-named local temporary tables created by the different processes. It does this by adding a numeric string to each local temporary table name left-padded by underscore characters. Although you specify the short name such as #MyTempTable, what is actually stored in TempDB is made up of the table name specified in the CREATE TABLE statement and the suffix. Because of this suffix, local temporary table names must be 116 characters or less.
If you remove the where from your code you will see that the table name is actually