Another Need Help for Choosing an SQL Server front end

Hi,
I'm just in the planning stages of upgrading a small bunch of databases
to MS SQL Server (2003). The current databases are very poorly
designed, so I'm basically starting from scratch. The databases will
grow to be quite large over time, and we have plenty of space for it.
Currently the number of users is about 15 in total. I would prefer to
web-enable it using our intranet since I have skills in programming JSP,
html, etc. But don't have time to learn ASP or ASP.Net. Am also
proficient with MS Access but have found it a little unstable in the
past.
Is there anything someone could recommend as a front-end?
AMH
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
"AMH" <anonymous@.blah.com> wrote in message
news:ukIxMAgHFHA.3244@.TK2MSFTNGP09.phx.gbl...
> I'm just in the planning stages of upgrading a small bunch of databases
> to MS SQL Server (2003). The current databases are very poorly
> designed, so I'm basically starting from scratch. The databases will
> grow to be quite large over time, and we have plenty of space for it.
> Currently the number of users is about 15 in total. I would prefer to
> web-enable it using our intranet since I have skills in programming JSP,
> html, etc. But don't have time to learn ASP or ASP.Net. Am also
> proficient with MS Access but have found it a little unstable in the
> past.
> Is there anything someone could recommend as a front-end?
There is no SQL Server 2003... 2000 is the current version. Microsoft Access
still makes a reasonably good front end. If the data is constantly being
changed by your users, you will need to learn to be proficient in multi-user
VBA coding techniques.
Steve
|||I can't see the users changing data so much. There'll be a lot of data
entry, and a lot of querying to find trends, patterns, etc.
AMH
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||When you buy sql server 2000 it comes already with a good GUI front end
called Enterprise Manager. It is very easy to use and you could control
who has access to what.
It is free too and can be installed on everybodies workstation.
|||But Enterprise Manager isn't designed to be a front end tool
for end users. It's a "quick and dirty" administration tool.
It's not necessarily free to distribute to everyone. It's
still governed by licensing.
-Sue
On 1 Mar 2005 16:41:48 -0800, thomasamillergoogle@.yahoo.com
wrote:

>When you buy sql server 2000 it comes already with a good GUI front end
>called Enterprise Manager. It is very easy to use and you could control
>who has access to what.
>It is free too and can be installed on everybodies workstation.
|||Thanks, but Enterprise Manager is more for the administrative side of
things - that's what I'll use. But I'm after a user interface that I
can build for the every-day user who can't have direct access to the raw
data.
AMH
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||"AMH" <anonymous@.blah.com> wrote in message
news:uYxTSzsHFHA.3376@.TK2MSFTNGP14.phx.gbl...
> Thanks, but Enterprise Manager is more for the administrative side of
> things - that's what I'll use. But I'm after a user interface that I
> can build for the every-day user who can't have direct access to the raw
> data.
One solution, use Microsoft Access as your front and create custom views in
SQL Server. The users never sniff the raw data tables
Steve

Another example of incomplete support of some legal database names

It has already been reported that the View tool in Enterprise Manager
cannot handle databases which have a period in their name (e.g.
"mydomain.com"). It doesn't show the individual field names.
Today I found a second problem: when scheduling a Job under SQL Server
Agent, in the New Step dialog you are prompted for a database name.
Databases with a period in their name are not listed. Tomorrow I'll
use ISQL to schedule the job in Windows Scheduler.
Hopefully MSFT will add these tests to the test scripts for the next
version and service pack (but don't hold your breath).
PS: I inherited this database name. It's too late (read: expensive)
now to fix it.
-Tom.Many of the tools do not support non-standard object names.
Even though SQL Server lets you create objects with invalid
names they aren't really legal names. You can find the rules
for object names in books online under the topic Using
Identifiers
-Sue
On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout
<tom7744@.no.spam.cox.net> wrote:

>It has already been reported that the View tool in Enterprise Manager
>cannot handle databases which have a period in their name (e.g.
>"mydomain.com"). It doesn't show the individual field names.
>Today I found a second problem: when scheduling a Job under SQL Server
>Agent, in the New Step dialog you are prompted for a database name.
>Databases with a period in their name are not listed. Tomorrow I'll
>use ISQL to schedule the job in Windows Scheduler.
>Hopefully MSFT will add these tests to the test scripts for the next
>version and service pack (but don't hold your breath).
>PS: I inherited this database name. It's too late (read: expensive)
>now to fix it.
>-Tom.|||On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout wrote:

>It has already been reported that the View tool in Enterprise Manager
>cannot handle databases which have a period in their name (e.g.
>"mydomain.com"). It doesn't show the individual field names.
>Today I found a second problem: when scheduling a Job under SQL Server
>Agent, in the New Step dialog you are prompted for a database name.
>Databases with a period in their name are not listed. Tomorrow I'll
>use ISQL to schedule the job in Windows Scheduler.
>Hopefully MSFT will add these tests to the test scripts for the next
>version and service pack (but don't hold your breath).
Hopefully not. I would prefer that MSFT removes the ability to call a
database "mydomain.com" or other pathological formats.

>PS: I inherited this database name. It's too late (read: expensive)
>now to fix it.
That's too bad.
I presume that you can still write scripts for all of the things that
you can't accomplish via the GUI? If so, then you have the tradeoff
costs of writing everything in scripts versus changing the name of the
database in the application (and all the associated testing).
--
"There is more to life than simply increasing its speed." - Mahatma Gandhi|||On Tue, 23 Mar 2004 21:32:35 -0700, Sue Hoegemeier
<Sue_H@.nomail.please> wrote:
You are correct. To my horror I found that:
sp_renamedb 'pubs', '123'
works, while BOL clearly has strict rules about the first character of
an identifier.
Would it kill MSFT to implement those rules, and not allow identifiers
that it later can't work with?
-Tom.
>Many of the tools do not support non-standard object names.
>Even though SQL Server lets you create objects with invalid
>names they aren't really legal names. You can find the rules
>for object names in books online under the topic Using
>Identifiers
>-Sue
>On Tue, 23 Mar 2004 19:39:31 -0700, Tom van Stiphout
><tom7744@.no.spam.cox.net> wrote:
>|||You could always send your request for this to
sqlwish@.microsoft.com
-Sue
On Wed, 24 Mar 2004 06:56:01 -0700, Tom van Stiphout
<tom7744@.no.spam.cox.net> wrote:
>On Tue, 23 Mar 2004 21:32:35 -0700, Sue Hoegemeier
><Sue_H@.nomail.please> wrote:
>You are correct. To my horror I found that:
>sp_renamedb 'pubs', '123'
>works, while BOL clearly has strict rules about the first character of
>an identifier.
>Would it kill MSFT to implement those rules, and not allow identifiers
>that it later can't work with?
>-Tom.
>

Analyze SqlServer 7.0 trace output

In one of our SqlServer 7.0 databases we get the following
error message:
Database AllWork: Transaction Log Backup...
Destination:
[e:\SQL7Data\BACKUP\AllWork\AllWork_tlog_200403290 853.TRN]
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4213:
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot
allow BACKUP LOG because file 'AllWork' has been subjected
to nonlogged updates and cannot be rolled forward. Perform
a full database, or differential database, backup.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or
restore operation terminating abnormally.
After a full database backup, everything is fine for some
time, but then the problem reoccurs.
I managed to capture a full trace using Profiler. At 7:40
the transaction log backup succeeded without errors and at
7:45 the transaction log backup failed with the
errormessage shown above. Allthough the trace is only 5
minutes, it still is over 1.100.000 records. I already
looked for SELECT INTO, WRITETEXT and UPDATETEXT
statements but I can't find any.
How can I determine what causes this error message?
What should I look for in the trace?
Any help would be appreciated,
TIA,
Gerrit van Ham
Gerrit,
Is 'select into/bulk copy' switched on? If so, there may be a bcp fast load taking place. I can't remember if this gets shown in the profiler trace in SQL7 or not - I don't think it does, but you may need to check this. It sounds like a bcp operation is t
aking place with select into/bulk copy switched on.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk

Analysis Services Processing Freezes or Hangs

Currently I have multiple Analysis Services databases on multiple servers. On occassion, when processing these databases it will freeze or hang. Sometime the problem is the database structure, sometimes it is the back end source tables being locked, etc. The only way I can terminate the processing is to kill the dev environment or management studio. This causes problems because the next time the database is opened, it will not process or save. The only solution I found is restarting Analysis Services. Is there some way to force stop processing without damaging the database and leaving connections open?

It might be possible to open a second instance of SSMS and use XMLA to discover the sessions or connections and then cancel the one that it stuck. But sometimes the server can take a while to respond to these commands if it is "stuck".

You can also use the xmlaDiscover class from the Analysis Services Stored Procedure project http://www.codeplex.com/ASStoredProcedures/Wiki/View.aspx?title=XmlaDiscover&referringTitle=Home which lets you manage this a bit simpler by running a command like:

CALL ASSP.DiscoverConnections()

which displays the current connections in a grid, and then:

CALL ASSP.CancelConnection(<ConnectionID>)

You should probably be aware that there is an issue with the Cancel command in SP2 that I read about in a KB article and sometimes it does not function correctly. Apparently there is a hotfix available if this issue affects you.

Analysis Services Admin access to one database only

On a given Analysis Server the machine level OLAP Administrators group controls which users have admin access to AS Databases and Cubes on that machine. From everything I have read, if you are in the OLAP Administrators group you have full access to administer ALL the databases and cubes.

We have a need to create a OLAP database and grant a few users (a role) full admin access to create and maintain datasouces and cubeswithin that database but NOT allow them admin access to the other existing databases and cubes on the server. This seems like such a common requirement. Has anyones else encountered and resolved this issue.

Thanks,

Tony

How about add the users to 'dbo' role in that OLAP database?|||The concept of "dbo role" does not exist for AS databases