Showing posts with label default. Show all posts
Showing posts with label default. Show all posts

Friday, March 30, 2012

Long text in "Default value or Binding"

Hey guys, how can I use a long text as default value in my database (column properties)?
I tried to paste my 10 row text into the field but it will only paste the first row as default value.

any ideas??What's the data type and data length of the column to which you paste text? And where did you paste your 10 row text into database?|||data type: text

It's obviosuly working fine if I create an update command updating the database with the same text. All I want is to have this text as default value for the column. But only the first row will be pasted...

SQL Server Mgmt-studio - Column Properties - default value or binding. Just a lil frustrating :)|||

OK now I understand youSmile Unfortunately this seems to be a flaw of Management Studio GUI, while you can add multiple lines as default in Enterprise Manager in SQL2000Surprise However we can define multiple-line default value by using T-SQL. New a query and use such statement:

ALTER TABLE dbo.test2 ADD CONSTRAINT
DF_Table1_description DEFAULT'The general steps are:

Back up the source database, which can reside on an instance of SQL Server 7.0, SQL Server 2000, or SQL Server 2005. The computer on which this instance of SQL Server is running is the source computer.

.'FOR description

sql

Monday, March 12, 2012

Logins created by default

Besides BUILTIN\Administrators and sa, are there any logins which will be
created by default in SQL Server 2000? It seems that a Windows User (the
user who installs the SQL Server) will be also created automatically.
Does using Windows Authentication or mixed mode affect which logins will be
created automatically?
Thanks."Peter" <Peter@.discussions.microsoft.com> wrote in message
news:C1A65A74-296D-4681-921F-71399767BB6B@.microsoft.com...
> Besides BUILTIN\Administrators and sa, are there any logins which will be
> created by default in SQL Server 2000? It seems that a Windows User (the
> user who installs the SQL Server) will be also created automatically.
Those are the default accounts...

> Does using Windows Authentication or mixed mode affect which logins will
be
> created automatically?
No.
Steve|||Steve,
I understand the sa and BUILTIN\Administrators are default accounts for both
Windows Authentication and Mixed mode.
But how about the Windows User login? It seems that it is created
automatically and it is the Windows User who installs the SQL Server. Is my
understanding correct?
"Steve Thompson" wrote:

> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:C1A65A74-296D-4681-921F-71399767BB6B@.microsoft.com...
> Those are the default accounts...
>
> be
> No.
> Steve
>
>|||Not unless that user is a member of the local Administrators Group.
So, any local admin has Windows Auth access to the server by default. It
doesn't matter who ran setup per se.
Local admin privleges are required to install services.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
I'm trying to find out the following:
1. Whether that Windows User login(the one installed the SQL Server) is
always created automatically during installing a SQL Server using Windows
Authentication or not.
Based on my testing in installing SQL Server with Windows Authentication
when I logged onto the domain, the following logins are created automaticall
y:
sa
BUILTIN\Administrators
domain\user - the Windows User who logged onto the domain
2. Can a user who has local administrative permissions log on to the
operating system locally (so he/she is not logged onto the domain) and
install a SQL Server using Windows Authentication? If yes, since the user
only logs on locally, I guess that only sa and BUILTIN\Administrators logins
are created automatically. Am I right?
So, basically I want to know what logins are created automatically in
installing a SQL Server using Windows Authentication when:
1. the user is logged on locally
2. the user is logged onto the domain
Thanks.
"Kevin McDonnell [MSFT]" wrote:

> Not unless that user is a member of the local Administrators Group.
> So, any local admin has Windows Auth access to the server by default. It
> doesn't matter who ran setup per se.
> Local admin privleges are required to install services.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||I think the confusion may be in that the account specified to start the
services is added to the logins.
If you specify in setup that a local windows account or domain account
should be used to start the services, (MSSQL and SQL Agent)
then this account is added to the logins.
If you selected to start the service with 'localsystem' which I don't
recommend, then only the Builtin\admin and sa account is
added to the logins.
Hope this helps.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Yes, I use a domain account to start MSSQL and SQL Agent. I don't remember
seeing any information about this account will be added to logins.
Thanks,
Peter
"Kevin McDonnell [MSFT]" wrote:

> I think the confusion may be in that the account specified to start the
> services is added to the logins.
> If you specify in setup that a local windows account or domain account
> should be used to start the services, (MSSQL and SQL Agent)
> then this account is added to the logins.
> If you selected to start the service with 'localsystem' which I don't
> recommend, then only the Builtin\admin and sa account is
> added to the logins.
> Hope this helps.
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Friday, March 9, 2012

loging in to sql express

I am trying to login into sql express using studio express and keep getting this msg.

"Cannot connect

....... under the default setting SQL Server does not allow remote connections. (provider: Named Popes Provider, error: 40 - could not open a connection to sql server) (sql server error2)"

I did try and make a change under surface area configuration to include local and remote connections but it did not help. Any thoughts? Thanks!

David

Are you using the SQL Server Browser service ? If not it could that that you might not use the default port of 1433. If so, type in the port number after the InstanceName using the syntax Servername\InstanceName,PortNumber which should be in your case something more specific Servername\SQLExpress,PortNumber


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||Jens, thanks. You gave me the idea to start using the browser service and I logged in that way.

Friday, February 24, 2012

Login problems with SQL Express edition.

Hi,

when running my application and trying to access an SqlServer express edition DB, I encounter the folowing error:

Cannot open user default database. Login failed.

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Does any one know how this problem can be resolved?

It is the SQL Server that comes togather with the VS2005.

Thank you!

The problem doesnt occure when i run the application using the default web server (cassini). It only occures when I run it using IIS.

But how can i run the application on IIS and use the DB?

Thnaks.

Login problem by not being in sysadmin group

Hi All

I experience a very strange login problem:

I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.

All is working well.

The moment remove sysadmin group from this login, i start getting errors:

Login failed for user 'test1'

... when I login from remote server. If I login from the same host - it continues with no problem.

When I go to sql server configuration manager, I see next:

sql native client configuration(32bit):

shared memeory enabled

tcp/ip enabled

named pipes enabled

VIA disabled

The same settings from sql server 2005 network configuration / protocols for mssqlserver

sql native client configuration / client protocols

sql 2005 surface area configuration / remote connections is configured:

local and remote connections (checked), using both tcp/ip and named pipes.

Does anybody have a clue?

What is the default database for your login?

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Hi Wesley

Default db is named 'test'. I made sure login has default db and can browse it.

|||

Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.

-Sue

Login problem by not being in sysadmin group

Hi All

I experience a very strange login problem:

I create standard security login, let say test1/test1 with a default db test and assign it sysadmin group.

All is working well.

The moment remove sysadmin group from this login, i start getting errors:

Login failed for user 'test1'

... when I login from remote server. If I login from the same host - it continues with no problem.

When I go to sql server configuration manager, I see next:

sql native client configuration(32bit):

shared memeory enabled

tcp/ip enabled

named pipes enabled

VIA disabled

The same settings from sql server 2005 network configuration / protocols for mssqlserver

sql native client configuration / client protocols

sql 2005 surface area configuration / remote connections is configured:

local and remote connections (checked), using both tcp/ip and named pipes.

Does anybody have a clue?

What is the default database for your login?

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Hi Wesley

Default db is named 'test'. I made sure login has default db and can browse it.

|||

Try changing the default database to master. If you can then connect with that login, there is a problem with the users access to what you were using for the default database.

-Sue