StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10165996
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-15T20:54:05.350
FavoriteCount
0
LastActivityDate
2012-04-15T20:54:05.350
LastEditDate
LastEditorUserId
0
OwnerUserId
61305
ParentId
10161004
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If all you want to do is print the names of the databases the table is in, your script can be much simpler (I fail to see the point of retrieving the table name and printing it every time - what could it be other than <code>SourceDestinations</code>?): <pre><code>DECLARE @sql NVARCHAR(MAX); SET @sql = N''; SELECT @sql = @sql + 'IF EXISTS (SELECT 1 FROM ' + QUOTENAME(name) + '.sys.tables WHERE name = ''SourceDestinations'') PRINT ''' + name + ''';' FROM sys.databases WHERE name LIKE 'PULL_%'; EXEC sp_executesql @sql; </code></pre> I suspect though that you want to do more with this once you've determined where the actual tables live. Ed is absolutely right, you can't concatenate a string to pass into sp_executesql as you are executing it, you must build it beforehand. This is true for all stored procedure calls, e.g. you can't say: <pre><code>EXEC sp_who2 'act' + 'ive'; </code></pre> Even though it should be the same thing as: <pre><code>EXEC sp_who2 'active'; </code></pre> You seem to know this already, at least to some extent, because you declared a <code>@sql</code> variable (though you never use it). I would change your code to: <pre><code>DECLARE d CURSOR LOCAL STATIC FORWARD_ONLY READ_ONLY FOR SELECT name FROM sys.databases WHERE name LIKE 'Pull_%'; DECLARE @db_name NVARCHAR(128), @sql NVARCHAR(MAX); OPEN d; FETCH NEXT FROM d INTO @db_name; WHILE @@FETCH_STATUS = 0 BEGIN PRINT @db_name; SET @sql = N'IF EXISTS (SELECT 1 FROM ' + QUOTENAME(@db_name) + '.sys.tables WHERE name = ''SourceDestinations'') PRINT ''' + @db_name + ''';' EXEC sp_executesql @sql; FETCH NEXT FROM d INTO @db_name; END CLOSE d; DEALLOCATE d; </code></pre> A couple of key points: <ol> <li>Don't use the default cursor options. In this case it's probably not a huge deal, but it's a bad habit to get into. I highlight one case of performance impact in this blog post: <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2011/03/08/t-sql-tuesday-16-this-is-not-the-aggregate-you-re-looking-for.aspx" rel="nofollow">http://sqlblog.com/blogs/aaron_bertrand/archive/2011/03/08/t-sql-tuesday-16-this-is-not-the-aggregate-you-re-looking-for.aspx</a></li> <li>Don't use <code>varchar(50)</code> for database/table names. These should be <code>nvarchar(128)</code> according to the rules for identifiers (<a href="http://msdn.microsoft.com/en-us/library/aa223962%28SQL.80%29.aspx" rel="nofollow">this doc is from 2000</a> but <a href="http://msdn.microsoft.com/en-us/library/ms175874.aspx" rel="nofollow">similar docs exist for newer versions</a>).</li> <li>Also you should be checking for schema as well. You may get multiple hits for <code>SourceDestinations</code> if someone has inadvertently created one in their own default schema.</li> <li>Your <code>@sql</code> string should probably be longer than 100 characters. I typically use <code>MAX</code> in these cases because the performance difference isn't worth sitting there wondering whether 255 or 1024 etc. will be enough characters.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSyntax error in sp_executesql
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAaron Bertrand
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.