db datatypes

Friday, March 30, 2012

Problem with long running report timing out

I have a 'YTD' report that is timing out after 30 minutes, where do I go to
change the default timeout period for reports?
TIA,
Bill Youngman
AnexinetIn SSRS2000, you open the Execution property for the report and select
the "Limit report execution to the following number of seconds:" option
under Report Execution Timeout. Then just set the number of SECONDS to
whatever amount will cover the proc run time.
I don't know if this is the same method used in SSRS2005 but I think
there'd be something similar. Hope this helps.
Bill Youngman wrote:
> I have a 'YTD' report that is timing out after 30 minutes, where do I go to
> change the default timeout period for reports?
> TIA,
> Bill Youngman
> Anexinet

Problem with logon SQL Server (MSDE)

Hi
I am working on a replication database system, I will use SQL Server Enterprise at the main database and I'm planning to have remote databases with MSDE, I installed MSDE in a remote computer using a valid logon account for the domain in the domain controller (I had it connected for the set up). If I disconnect the computer from the network an restart the machine the Sql Server won't start with the cache information.

How can I solve this problem?MSDE Doesn't support a login from the network; only from the local computer.

Am I right?

problem with loging in

I installed a default instance of Enterprise edittion and

didn't face any error during the instalation process.

In Management Studio in the Server Name section for loging in I wrote the name of the local system.

but I couldn't log in.

Control Panel \ administrative tools\services

there is no SQL Server service at all.

should I install any thing extra just like Express Edition which I used to install SQL Express in Visual Studio 2005 pakage or like MSDE in SQL Server 2000?

please tell me what to do

thanks.

pooyan

Hello,

It would seem that the core dbms has not been installed correctly - did you perhaps only select client tools during the install?

Reinstall the server components (make sure you run setup from the server, not tools folder).

Cheers,

Rob

Problem With Login Null

Hi,
I have a problem. My web server is a Windows 2k Server and my database
server a Windows 2003. I use windows authentication to login at SQL Server,
but when I access from a client machine that uses Win 2k Professional I
always receive this message: "[Microsoft][ODBC SQL Server Driver][SQL
Server]Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection.".
When I access from a client machine that uses Windows XP everything its
ok.
This problem only occurs at the web site. When I try to access the Query
Analyzer or the Enterprise Manager I still have the connection.
Can anyone help me?!
Thanks,
Riane Santos
riane@.cpunet.com.br
I've seen this error when a local security policy was in place preventing
access from the network. But, I don't see how that could be your problem
since it works from some machines.
"Riane de Oliveira Torres Santos" <riane@.cpunet.com.br> wrote in message
news:eI4Ehr1jEHA.2788@.tk2msftngp13.phx.gbl...
> Hi,
> I have a problem. My web server is a Windows 2k Server and my database
> server a Windows 2003. I use windows authentication to login at SQL
Server,
> but when I access from a client machine that uses Win 2k Professional I
> always receive this message: "[Microsoft][ODBC SQL Server Driver][SQL
> Server]Login failed for user '(null)'. Reason: Not associated with a
trusted
> SQL Server connection.".
> When I access from a client machine that uses Windows XP everything its
> ok.
> This problem only occurs at the web site. When I try to access the Query
> Analyzer or the Enterprise Manager I still have the connection.
> Can anyone help me?!
> Thanks,
> Riane Santos
> riane@.cpunet.com.br
>
sql

Problem With Login null

problem with login list

Hi,

I'm using the 64-bit version of SQL Server 2005, SP2, on Windows
Server 2003 R2 X64 Enterprise Edition. I've got a bunch of users out
there who are the db_owner, db_accessadmin and db_securityadmin of
their different respective databases. I would expect that they would
be able to add users to their databases, given that a login exists on
the server. However, when they go to browse logins to add a user in
Management Studio, they are only shown a very short list (like,
themselves and sa, and that's it). We have hundreds of logins on the
server, and they should be able to add any one of them to their
databases if they wish. And if they try to type in the login name
directly, they get a permission denied error.

I am the system administrator, so thankfully I've not experienced this
problem, and I can add users for them. But I'd rather they be able to
do it themselves as they see fit. I have experimented by creating a
test SQL-authenticated login, and making it db_owner of a test
database. When I login with that test login and try to add a user, I
see the exact same behavior. The only logins viewable are my test
login and sa. The only other thing I can add is it's not just
occurring with the GUI interface; the same thing happens when I do a
direct query on the master.sys.syslogins view: I only see the same two
logins. So it appears it's happening at that level and the result
appears up in the GUI.

It appears this is a security/permissions thing. Anyone know if
there's a configuration setting or something that might be preventing
non-privileged users from being able to view all the server logins
when attempting to add users to their databases, in which they are
assigned the db_owner role?

Thanks
GringoSkyGringo (doug@.bu.edu) writes:

Quote:

Originally Posted by

>
I'm using the 64-bit version of SQL Server 2005, SP2, on Windows
Server 2003 R2 X64 Enterprise Edition. I've got a bunch of users out
there who are the db_owner, db_accessadmin and db_securityadmin of
their different respective databases. I would expect that they would
be able to add users to their databases, given that a login exists on
the server. However, when they go to browse logins to add a user in
Management Studio, they are only shown a very short list (like,
themselves and sa, and that's it). We have hundreds of logins on the
server, and they should be able to add any one of them to their
databases if they wish. And if they try to type in the login name
directly, they get a permission denied error.

They need to have VIEW DEFINITION on the logins they need to add. There
is no permission VIEW ANY LOGIN, but there is a server-level VIEW ANY
DEFINITION you can grant to them, but I would think twice before you
did.

Quote:

Originally Posted by

The only other thing I can add is it's not just occurring with the GUI
interface; the same thing happens when I do a direct query on the
master.sys.syslogins view: I only see the same two logins. So it
appears it's happening at that level and the result appears up in the
GUI.

It appears that you are of the old SQL 2000 school. :-)

Microsoft did a lot around security in SQL 2005, and one thing is
that objects are no longer visible to everyone. Essentially, you
can only see an object, if you have permission to it.

And the place to look for logins these days, is sys.server_principals.
While the old system tables are around for compatibility, they may not
show aspects that are new to SQL 2005.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

problem with login

I have a problem with login on slq server 2005 on the other machine. The story is:

I have been trying create classes with help of SqlMetal (Linq tool) and all the time i have a message

Unhandled Exception: System.Data.SqlClient.SqlException: Login failed for user 'me'

So, I tried connect by sqlcmd.

sqlcmd -S OURSERVER -d database -U me -P password

And the error message is:

Msg 18456, Level 14, State 1, Server OURSERVER, Line 1
Login failed for user 'me'.

and...

I CAN connect to this database with help of "SQL Server Management Studio Express"

with the same username and password.

thanks for help

bakuuu

ps. sorry for my english

From your description, I don’t have enough information to determine if my following assumption is correct or not, but it may be worth a try.

I am guessing that the scenarios that fail (1) & (2) are from a remote machine, but the one that succeeds (3) is on the same machine as SQL Server Express. If this is true, it may be possible that TCP communications are disabled and/or the windows firewall is not allowing to connect. Please use SQL Server Configuration Manager to enable TCP (and restart the server) and make sure the firewall allows the connection.

Another possibility is that the DB “database” specified with the parameter –d is not available or you don’t have permission to connect. Try using the default DB (remove the –d database parameter) or master (-d master).

If my assumptions are not correct, we will appreciate further information in order to help.

Thanks a lot.

-Raul Garcia

SDE/T

SQL Server Engine