Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...SQL Express 2008 R2 issueSQL Express 2008 R2 issue
Previous
 
Next
New Post
4/30/2012 1:58 PM
 
This is very strange! I have created my database on SQL 2008 Express R2 and connected it to DNN and all works fine. I can logon the site and I can use SQL on the site to run queries...all is well. BUT, on the server when I start Server Management Studio, I can't see the tables nor can I query them. The database is there, I can expand all the sections...but I can't see anything. No tables, No stored procedures, No views. I have logged on with several accounts... Windows administrator (win authentication), SA, and even the same user that I am using for DNN access and NONE can see the tables. Am i going crazy....or what! I hope someone can help me with this.
 
New Post
4/30/2012 2:04 PM
 
most likely, you are using the DNN default database (/app_date/database.mdf) file in user instance mode, without being attached to the server. please read for details: http://www.dotnetnuke.com/Resources/Blogs/EntryId/1202/DNN-SQLExpress-SQL-Server-Management-Studio.aspx

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/30/2012 2:18 PM
 
Thanks Leupold, but I think it is a bug. I found this post from Microsoft...I just need to know where to change this setting.

Posted by Microsoft on 4/28/2009 at 11:13 PM
Hi,
This is a bug in SMO. We are planning to fix this by next major release which will be SQL11.
This bug is actually not related to schemas at all but is related to the table owners. When we try to get the tables from the server in SMO, because of performance reasons we try to get their owners too by doing an INNER JOIN. Hence, if the user doesn’t have permissions to view the table owners, he is not able to see the tables also using SMO which is a bug.
Hence the workaround for this is, provide view permissions to the user on all the owners of the table. -Microsoft

So, Now where the heck do I set the permissions to view table owners??

-Mike
 
New Post
4/30/2012 2:20 PM
 
please check your connection string (UNCOMMENTED version!!!) if it contains a file name, you are not using an attached database.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/30/2012 6:47 PM
 

Yes, you were right about it pointing to a file name. I had to re-install with a newer version to get around the problem....but it is working now and I can see the tables in Server Management. Thank you very much for pointing me in the right direction.  It's great to have a knowledge source like yourself to get answers.

THANKS AGAIN!

-Michael

 
Previous
 
Next
HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...SQL Express 2008 R2 issueSQL Express 2008 R2 issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out