Database Standards HELP!

I would like to create a new database and follow some standard. I am hoping that there is some ANSI documentation or Microsoft documentation on a NAMING standard when creating objects in the database.
i.e Table name "tblEmployees"
Column name "txtLastName"

Is there any GOOD documentation on creating a database using a PROVEN, and ACCEPTED standard?

Hi HotChick -

I always rebel and do whatever I want.......but, here is a pretty decent link:http://vyaskn.tripod.com/object_naming.htm

|||The accepted standard is ISO 11179. http://metadata-standards.org/Document-library/Draft-standards/11179-Part5-Naming&Identification/

database server Link DOWN

Hi every body.

We have instaled Sql Server 2000 Standard Sp4, whit a Nortel Product. That aplication make to gestion calls using MSQL2000; in some moment the DB stoping and the Reason is "[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Arithmetic overflow error for data type smallint, value = 33459."

We do not have any idea about this problem.

Thx

Eliseo Berdugo

Hi, try to desinstal and reinstall your "Driver for JDBC".

Database Restore caused production server reboot

I got a production server with the following hard ware software
Server: Dell PowerEdge 2950
Storage: FS SAN 650
Memory: 4GB
windows 2003 standard (sp1)
sql server 2005 standard (9.00.2153)
There are five user databases, their size range varies from 12GB to 15 GB
I wanted archived data from one of the databases, so started database
restore process from old backups that made server to freeze then rebooted it
automatically. I found the following messages in the event log. My question
is how a restore process will bring server shutdown. With the same memory
and i had 150 databases in dev environment and never got a server reboot
with database restore. Can you please let me know your expert ideas what
else might have caused the reboot if not the restore process.
Date 2/19/2008 11:15:48 AM
Log Windows NT (Application)
Source MSSQL$xxx
Category Logon
Event 3221242661
Computer xxxxxx
Message
SQL Server failed with error code 0xc0000000 to spawn a thread to process a
new login or connection. Check the SQL Server error log and the Windows
event logs for information about possible related problems. [CLIENT:
111.111.11.164]
Date 2/19/2008 11:22:09 AM
Log Windows NT (Application)
Source MSSQL$xxxxx
Category Logon
Event 3221242666
Computer xxxxxxx
Message
The server was unable to load the SSL provider library needed to log in; the
connection has been closed. SSL is used to encrypt either the login sequence
or all communications, depending on how the administrator has configured the
server. See Books Online for information on this error message: 0x2746.
[CLIENT: 111.111.111.5]
-- --
Thanks,
Subbu
Hi
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1308037&SiteID=1
http://www.sqlservermart.com/resources/SynAttackProtect.aspx
"Subbu" <subbudamireddy@.hotmail.com> wrote in message
news:%23g0IhlWdIHA.3400@.TK2MSFTNGP03.phx.gbl...
>I got a production server with the following hard ware software
> Server: Dell PowerEdge 2950
> Storage: FS SAN 650
> Memory: 4GB
> windows 2003 standard (sp1)
> sql server 2005 standard (9.00.2153)
> There are five user databases, their size range varies from 12GB to 15 GB
> I wanted archived data from one of the databases, so started database
> restore process from old backups that made server to freeze then rebooted
> it automatically. I found the following messages in the event log. My
> question is how a restore process will bring server shutdown. With the
> same memory and i had 150 databases in dev environment and never got a
> server reboot with database restore. Can you please let me know your
> expert ideas what else might have caused the reboot if not the restore
> process.
> Date 2/19/2008 11:15:48 AM
> Log Windows NT (Application)
> Source MSSQL$xxx
> Category Logon
> Event 3221242661
> Computer xxxxxx
> Message
> SQL Server failed with error code 0xc0000000 to spawn a thread to process
> a new login or connection. Check the SQL Server error log and the Windows
> event logs for information about possible related problems. [CLIENT:
> 111.111.11.164]
>
> ----
> Date 2/19/2008 11:22:09 AM
> Log Windows NT (Application)
> Source MSSQL$xxxxx
> Category Logon
> Event 3221242666
> Computer xxxxxxx
> Message
> The server was unable to load the SSL provider library needed to log in;
> the connection has been closed. SSL is used to encrypt either the login
> sequence or all communications, depending on how the administrator has
> configured the server. See Books Online for information on this error
> message: 0x2746. [CLIENT: 111.111.111.5]
> -- --
> Thanks,
> Subbu
>
>
>

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
Chris
You might be able to attach the database files to the new installation. Read about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris
|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:

> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>
|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HD
D
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read
about sp_attach_db.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup
in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old
HDD
> is now visible and accessible. I can now comfortably recover all their dat
a
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:

> You might be able to attach the database files to the new installation. Re
ad about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>|||> Tibor Im curious about your response. You say he "might" be able to attach,">
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously deta
ched from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work".
Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appre
ciate if MS would
provide a technical elaboration about specifically when attach work and when
it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we
see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me.
Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...[vbcol=seagreen]
> Tibor Im curious about your response. You say he "might" be able to attach
,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>

database recovery

The SBS 2003 server is blue screening. The client has not done any backup in
several months. I have pluged in another HDD, installed Standard 2003 and
then reconnected the old HDD as a second drive. All the data from the old HDD
is now visible and accessible. I can now comfortably recover all their data
except SQL database. Is there any way? Please help. Thanks in advance.
ChrisYou might be able to attach the database files to the new installation. Read about sp_attach_db.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> The SBS 2003 server is blue screening. The client has not done any backup in
> several months. I have pluged in another HDD, installed Standard 2003 and
> then reconnected the old HDD as a second drive. All the data from the old HDD
> is now visible and accessible. I can now comfortably recover all their data
> except SQL database. Is there any way? Please help. Thanks in advance.
> Chris|||Tibor Im curious about your response. You say he "might" be able to attach,
what circumstances make this possible?
"Tibor Karaszi" wrote:
> You might be able to attach the database files to the new installation. Read about sp_attach_db.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
> > The SBS 2003 server is blue screening. The client has not done any backup in
> > several months. I have pluged in another HDD, installed Standard 2003 and
> > then reconnected the old HDD as a second drive. All the data from the old HDD
> > is now visible and accessible. I can now comfortably recover all their data
> > except SQL database. Is there any way? Please help. Thanks in advance.
> >
> > Chris
>|||As long as there was no physical damage to the data or log files it should
work. When it attaches it will go thru recovery and roll forward or back as
needed to make the db consistent.
--
Andrew J. Kelly SQL MVP
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to
> attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation.
>> Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any
>> > backup in
>> > several months. I have pluged in another HDD, installed Standard 2003
>> > and
>> > then reconnected the old HDD as a second drive. All the data from the
>> > old HDD
>> > is now visible and accessible. I can now comfortably recover all their
>> > data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>|||> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
Below is a quote from Books Online (2000) , sp_attach_db
"sp_attach_db should only be executed on databases that were previously detached from the database
server using an explicit sp_detach_db operation. "
We see posts almost here daily about "... crash ... attach... doesn't work". Granted, many of these
deleted the log file as well, but still. I like to play safe. Yes, I'd appreciate if MS would
provide a technical elaboration about specifically when attach work and when it doesn't. But without
such, I feel that BOL is the one to trust. Especially based on the posts we see here. Even if attach
(without detach) work in 99.99 % of the cases, it isn't good enough for me. Without knowing why it
won't work, I can't trust it. :-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:ECD839A1-AC24-45BC-94D2-306A82B9397C@.microsoft.com...
> Tibor Im curious about your response. You say he "might" be able to attach,
> what circumstances make this possible?
> "Tibor Karaszi" wrote:
>> You might be able to attach the database files to the new installation. Read about sp_attach_db.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Chris Toffa" <ChrisToffa@.discussions.microsoft.com> wrote in message
>> news:289C92F0-38BF-40DE-B60D-D464F876DBCC@.microsoft.com...
>> > The SBS 2003 server is blue screening. The client has not done any backup in
>> > several months. I have pluged in another HDD, installed Standard 2003 and
>> > then reconnected the old HDD as a second drive. All the data from the old HDD
>> > is now visible and accessible. I can now comfortably recover all their data
>> > except SQL database. Is there any way? Please help. Thanks in advance.
>> >
>> > Chris
>>

Database Output Problem for a SQL Server 2000 stored procedure

Hi,

I have a problem with "database output" window in executing a select-sp in vs 2005 standard. The db is a sql server 2000 one.

When I execute the sp within VS, the database output correctly displays the execution information:

No rows affected.
(1 row(s) returned)
@.RETURN_VALUE = 3

but I can't see the returned rows (3 rows are returned); I only see the column names and no data.

Running [dbo].[spBkm_GetList] ( @.IDUser = <DEFAULT>, [.......]).
IDBkm UIBkm IDUser
------- ------------ ---No rows affected.

If I run the same sp in Sql Server Manager Studio Express it correctly shows the data of the 3 rows returned.

The sp uses

EXECsp_executesql @.Sql, @.ParamList, .....

for executing the sql statement and the last line of sp is

RETURN@.@.ROWCOUNT

I've tried removing the "RETURN @.@.ROWCOUNT" with no success.

The problem affects only one sp, the others, which are absolutely similar, work properly .

I don't know what is the problem...

Any idea?

Thanks in advance

Ive' resolved the problem in a strange way, it seems to me a bug...

If I exclude from the select statement a field of type uniqueidentifier, alla data are correctly displayed!

I've tried on other sp and the behaviour is the same.

Hope this may help someone else with the same problem...