Remove [Identifier delimiter]'s

in SQL 2005 in the Management Studio when I right click a table and script to new window the output includes the Identifier delimiter i,e. [FIELD_NAME] I would like these off by default.. for the life of me I can't find out if or where this is done...

Can anyone help please?

Best Regards

Jon

I wonder why you would want to do this as it is proper T-Sql syntaxsql

Removal of Dimension Name from Data Sample Viewer

Hi All,

I have created a DrillThrough Action in my cubes. When I right-clicked on the data cell and click the Drillthrough action, the Data Sample Viewer pop-up. The Data Sample Viewer always contain a $ sign and the dimension name. Is there a way to remove the dimension name?

Thanks

Chen Khoon Seah

What application you are using to browse your cube?

Try installing beta of Office 2007 and trying invoking your drillthough action in Excel.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks Edward. Currently I am using Microsoft Visual Studio. Will be installing Office 2007 to try it out. Thanks again.

remote debug problem

I am trying to do remote debugging and doesn't seem to be working....I brin
g up query analyzer, select the datbase, select the sp, right click debug, e
nter a value and ok...when I do this it doesn't pass/break...it completes
the query and grays out the
buttons at the top....
steps I have done:got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:

> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you righ
t click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow acces
s permission
> b. under applications tab - I went to properties ont he sqldbreg ed
ited the use custom access permission under security to allow everyone permi
ssion
> c. on that same com(sqldbreg) - I changed the identity to use a the
local user I setup with admin rights
> what else can I try?

remote debug problem

I am trying to do remote debugging and doesn't seem to be working....I bring up query analyzer, select the datbase, select the sp, right click debug, enter a value and ok...when I do this it doesn't pass/break...it completes the query and grays out the
buttons at the top....
steps I have done:
got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:

> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you right click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow access permission
> b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
> c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
> what else can I try?

Remote Connection Problems

I am not able to register a remote server and connect to
it currently without going through this process:
1. Open "My Network" and click on "Entire Network"
2. Search for the SQL Server by host and domain name (i.e.
host.domain.com)
3. Sign in with a valid username and password
4. Connect to the SQL Server through MMC
Does anyone know why I need to establish the Windows
Authentication first? Shouldn't I be able to connect with
just SQL Authentication?Hi Shannon,
For Windows Authentication, SQL Server takes your current Windows user
details. That's useful if you are in the same domain. Sounds like you aren't
in the same domain and Windows is establishing a new set of credentials when
you navigate to the system. Those credentials are then being used by SQL
Server.
SQL Server authentication requires separate users to be set up inside SQL
Server (ie not Windows users).
HTH,
--
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shannon Burns" <sburns875@.hotmail.com> wrote in message
news:068101c364c2$b38e3420$a301280a@.phx.gbl...
> I am not able to register a remote server and connect to
> it currently without going through this process:
> 1. Open "My Network" and click on "Entire Network"
> 2. Search for the SQL Server by host and domain name (i.e.
> host.domain.com)
> 3. Sign in with a valid username and password
> 4. Connect to the SQL Server through MMC
> Does anyone know why I need to establish the Windows
> Authentication first? Shouldn't I be able to connect with
> just SQL Authentication?