I don't even think I should try to store the security tables in DB2, agree?



So I will just have a separate SQL instance for security? I am fine with that and see pretty detailed instructions on how to support the tables in a separate database.



Just really making sure I didn't miss anything here. Does the above sound solid to you?



Also, how would this work if I decide to architect my application so that it will support a truly "disconnected mode" as in I just found out that users might need to run it at times on a laptop with no internet access, then save the data to the server at a later time. I was going to just use XML or a local SQLEXPRESS or SQL Compact database, but I'm not sure how not being able to connect to the security tables will work in that scenario.




Keith Chisarik

did this question slip through the cracks?



much appreciated.

Keith Chisarik

Hey Keith,

I guess it slipped through -- or it was not important to us or something.

Yes I totally agree, it would be very problematic... Use SQLServer Express install the security tables with all of its data and connect to it via normal means.  I assume you are not going to maintain the Security tables on the disconnected Laptop, if so this will present another set of problems..

Hope this helps, Steve..

No we aren't going to maintain the security tables on the laptops when disconnected from the server but if I cannot access the server where the security data is stored, will things work? I haven't used security much so please excuse the questions.



I will need to have the application be able to run in a truly disconnected mode, I plan to have a "snapshot" feature that will allow users to take a copy of the data they need to local XML files or a local SQL database (leaning toward XML heavily) that will allow them to work offsite, then they can add their changes when they are back in the office.



How will this model work (or not work) using the RBS?



Thank you for your time.

Keith Chisarik

I think your best bet would be to use SQL Server 2005 Compact:

http://www.microsoft.com/sql/editions/compact/sscecomparison.mspx

It's basically an expanded version of MS Access: just an *.mdf file on disk that can be accessed as if it was a SQL Server.  So, since you only need the local data it's perfect for you since you won't have to provide access to more than one user, and the RBS won't know the difference.  Keeps you from having to install SQL Server 2005 Express.

OK then so part of my "snapshot" of the data would include all the RBS tables and I should be good to go?

Keith Chisarik

Yep, just use some utility to wipe the *.mdf and copy over the RBS data and you'll be good to go.  Don't forget that you can put anything else you want in that *.mdf file.  And you can have several *.mdf files for other stuff.