Destination List Not Filled


Author
Message
Bill Cunnien
Bill Cunnien
StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)
Group: Forum Members
Posts: 785, Visits: 3.6K
I am trying to test the deployment of the security tables to my test server from which the application runs.  I setup a profile in the DDT, then began the wizard.  After selecting Role Based Security Type for the DDT, I was then asked about the source DB.  Of course, this is the local SSE2005 database used only by my development environment.  That was no problem.  When I go to the next window, I am asked about the destination database.  The drop down list is not populated.  I cannot choose anything.  I clicked finished anyway (knowing I would get an error) and I received an error box with the typical object not found error.  I clear the error window and now I am stuck on the wizard.  I cannot cancel, break, esc or anything.  Time to kill the process.

What do I need to do to fill that list of potential destinations?

Thanks,
Bill

Replies
Greg McGuffey
Greg McGuffey
Strategic Support Team Member (4.8K reputation)
Group: Forum Members
Posts: 2K, Visits: 6.6K
Here's what I think is happening...the database table is named 'master', not 'Master'. The casing is wrong. This is not something that I am able to fix. What can I do, now?


SQL server doesn't care about casing. So...



Use master



and



Use master



both work.
Trent Taylor
Trent Taylor
StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)StrataFrame Developer (14K reputation)
Group: StrataFrame Developers
Posts: 6.6K, Visits: 7K
Actually, the defaults were changed on your server to be case sensitive...this is generally a bad idea.  There are certain developers out there that swear by case-sensitive SQL Servers, but it can complicate things, as you have learned.  When you install SQL Server, by default, it will assume Case-Insensitive.  You can change this through the SQL Server Management Studio, but this is what is happening to you...good eye Smile
Bill Cunnien
Bill Cunnien
StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)StrataFrame VIP (1.2K reputation)
Group: Forum Members
Posts: 785, Visits: 3.6K
The old SQL Server on which I placed the app data is one of the original RDBMSs in our company.  It started at v7 (maybe even 6.5!) and one of the requirements by the software that we bought it for was case-sensitivity.  It is often a headache to work around.  That is why I got a second SQL Server to do the other heavy lifting.  The main app data will have to reside on the old one, unfortunately.
Greg McGuffey
Greg McGuffey
Strategic Support Team Member (4.8K reputation)
Group: Forum Members
Posts: 2K, Visits: 6.6K
Actually, the defaults were changed on your server to be case sensitive...


Jeesh, I completely forgot about that option. Blush



There are certain developers out there that swear by case-sensitive SQL Servers, but it can complicate things, as you have learned.


I certainly understand swearing at developers who turn this option on... w00t
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View
Threaded View
Bill Cunnien - 18 Years Ago
Ivan George Borges - 18 Years Ago
StrataFrame Team - 18 Years Ago
Bill Cunnien - 18 Years Ago
Ivan George Borges - 18 Years Ago
Ivan George Borges - 18 Years Ago
                         I went ahead and clicked next on the empty grid. It didn't do...
Bill Cunnien - 18 Years Ago
                             Here's what I think is happening...the database table is named...
Bill Cunnien - 18 Years Ago
                                 I went ahead and stuck the security package on another server. The...
Bill Cunnien - 18 Years Ago
                                     Naturally, the SecurityDataSourceKey. I added my DataLayer.DataSource...
Bill Cunnien - 18 Years Ago
                                         Well, I thought it was simple. Another error has popped up. The server...
Bill Cunnien - 18 Years Ago
                                             Solved. :D It had to be in the data source string. So, after...
Bill Cunnien - 18 Years Ago
                                                 LOL...glad you found your problem :)
Trent L. Taylor - 18 Years Ago
                                         Yup...you found it. The SecurityDataSourceKey tells the RBS BOs which...
Trent L. Taylor - 18 Years Ago
                                 [quote]Here's what I think is happening...the database table is named...
Greg McGuffey - 18 Years Ago
                                     Actually, the defaults were changed on your server to be case...
Trent L. Taylor - 18 Years Ago
                                         The old SQL Server on which I placed the app data is one of the...
Bill Cunnien - 18 Years Ago
                                         [quote]Actually, the defaults were changed on your server to be case...
Greg McGuffey - 18 Years Ago

Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search