Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hog
Constraint Violating Yak Guru
284 Posts |
 Posted - 2005-06-10 : 03:50:38
|
Following on from what I have learned here, (from spirit1  ), is it good/safe practice to create a global variable table which cna then be passed as part of a string parameter into another batch? |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2005-06-10 : 04:16:11
|
i don't think it's good or bad... the answer is it depends.global tables are great for cross batching.however there are a few things you must consider.in a multiuser enviroment global tables are usualy not very welcome because they can lead to bad data.if you use them for administration or something similar then i'm all for it.usually things can be done in a way that doesn't even require a global temp table.they can be a great tool if used properly but also a quite nice app buster if misused Go with the flow & have fun! Else fight the flow  |
 |
|
|
hog
Constraint Violating Yak Guru
284 Posts |
Posted - 2005-06-10 : 04:38:17
|
| Aha, I shall therefore stick to the temp table approach!Ta |
|
|
|
|
|
|
global variable table