June 10, 2011 at 2:57 pm
Having a challenge with a table that we know exists and is useable. We know the query works as we have tested it out in SSMS just fine. However, when running the report or just running the data set in Query Designer (while developing in BIDS) the error message:
Invalid object name 'dbo.myTable'
The data source is correct. The permissions are mine when running in either place, and I have full permissions.
Has anyone had a similar situation? I keep thinking there's a place to refresh the data set, data source, cache, ... something... but haven't found a real solution yet.
June 10, 2011 at 5:23 pm
Was this dataset created from scratch? I have seen this occur when an existing dataset was used and redefined to be a new dataset.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 13, 2011 at 11:14 am
I don't believe it was new. A colleague of mine is working on this so I will check with her. But I believe she imported the report (moving from 2005 to 2008) and is updating it based on new requirements. I'll ask her to try creating a new dataset and see how it goes.
Thanks for the lead.
June 13, 2011 at 11:19 am
Are you pointing on the correct db / server?
June 16, 2011 at 7:03 am
My coworker tried creating a new dataset and this did not resolve the issue. For the question about the database, yes, that was one of the first things we checked. We're in the middle of an upgrade from not only 2005 to 2008 but also of our software which has a completely different table structure. We've imported and updated quite a few reports without any errors. This one is rather frustrating. As I said in post 1, we know the query works but there must be something in the new version of BIDS that we're missing... maybe something simple similar to the IntelliSense refresh in the SSMS 2008. Any more takers???? :alien:
June 16, 2011 at 7:05 am
The only thing I can think of it to try to rebuild the report from scratch, staring with that query.
Kind of a last ditch resort but I've seen it work a few times.
June 16, 2011 at 9:48 am
I have had similar happen to me - rebuild from scratch as Ninja said seems to work.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 16, 2011 at 9:53 am
SQLRNNR (6/16/2011)
I have had similar happen to me - rebuild from scratch as Ninja said seems to work.
The the default fix for most M$ products :hehe:.
June 16, 2011 at 10:22 am
Ninja's_RGR'us (6/16/2011)
SQLRNNR (6/16/2011)
I have had similar happen to me - rebuild from scratch as Ninja said seems to work.The the default fix for most M$ products :hehe:.
Unfortunate, but rings true. Back to fixing my windows install.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 16, 2011 at 10:24 am
SQLRNNR (6/16/2011)
Ninja's_RGR'us (6/16/2011)
SQLRNNR (6/16/2011)
I have had similar happen to me - rebuild from scratch as Ninja said seems to work.The the default fix for most M$ products :hehe:.
Unfortunate, but rings true. Back to fixing my windows install.
:hehe::w00t::-D:Whistling:
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply