\Backup directories - remove safely?

I've successfully applied SP4 to an MSDE 2000 installation on a
Windows 2000 Professional system. Now I've notived several \Backup
subdirectories in the "Microsoft SLQ Server" directory. Since I don't
want to go back to any previous version, these subdirectories appear
to be no longer required. May I safely remove them?
Heinz Wehner
(Karlsruhe, Germany)
Hi,
No problems. You can delete that directory.
Thanks
Hari
SQL Server MVP
"Heinz Wehner" <hwehner@.hotmail.com> wrote in message
news:c215e1ppe9k9vqim24ckphf0eukkgr6n5a@.4ax.com...
> I've successfully applied SP4 to an MSDE 2000 installation on a
> Windows 2000 Professional system. Now I've notived several \Backup
> subdirectories in the "Microsoft SLQ Server" directory. Since I don't
> want to go back to any previous version, these subdirectories appear
> to be no longer required. May I safely remove them?
> Heinz Wehner
> (Karlsruhe, Germany)
|||Thanks Hari.

> On Sun, 24 Jul 2005 19:32:03 +0530,
> Hari Prasad <hari_prasad_k@.hotmail.com> wrote:
> Hi,
> No problems. You can delete that directory.
> Thanks
> Hari
> SQL Server MVP
>
> Heinz Wehner <hwehner@.hotmail.com>
> wrote in message news:c215e1ppe9k9vqim24ckphf0eukkgr6n5a@.4ax.com...
> I've successfully applied SP4 to an MSDE 2000 installation on a
> Windows 2000 Professional system. Now I've notived several \Backup
> subdirectories in the "Microsoft SLQ Server" directory. Since I don't
> want to go back to any previous version, these subdirectories appear
> to be no longer required. May I safely remove them?
> Heinz Wehner
> (Karlsruhe, Germany)
sql

[novice Q] sequence in restoring system db

hi,
is there sequence in restoring system db?
shall i start with master, msdb followed by temp or the sequence doesnt
matter?
TIA"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> hi,
> is there sequence in restoring system db?
> shall i start with master, msdb followed by temp or the sequence doesnt
> matter?
> TIA
You will need to restore the master db first. You should check the BOL on
restoring the master database.
Do a search for "Restoring the master Database from a Current Backup"
After that, the other databases order doesn't matter a whole lot.
You do not restore tempdb, it is recreated every time the SQL Server is
restarted.
Rick Sawtell
MCT, MCSD, MCDBA|||got it...thanks rick
"Rick Sawtell" wrote:
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> > hi,
> > is there sequence in restoring system db?
> > shall i start with master, msdb followed by temp or the sequence doesnt
> > matter?
> >
> > TIA
> You will need to restore the master db first. You should check the BOL on
> restoring the master database.
> Do a search for "Restoring the master Database from a Current Backup"
> After that, the other databases order doesn't matter a whole lot.
> You do not restore tempdb, it is recreated every time the SQL Server is
> restarted.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

[novice Q] sequence in restoring system db

hi,
is there sequence in restoring system db?
shall i start with master, msdb followed by temp or the sequence doesnt
matter?
TIA
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> hi,
> is there sequence in restoring system db?
> shall i start with master, msdb followed by temp or the sequence doesnt
> matter?
> TIA
You will need to restore the master db first. You should check the BOL on
restoring the master database.
Do a search for "Restoring the master Database from a Current Backup"
After that, the other databases order doesn't matter a whole lot.
You do not restore tempdb, it is recreated every time the SQL Server is
restarted.
Rick Sawtell
MCT, MCSD, MCDBA
|||got it...thanks rick
"Rick Sawtell" wrote:

> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> You will need to restore the master db first. You should check the BOL on
> restoring the master database.
> Do a search for "Restoring the master Database from a Current Backup"
> After that, the other databases order doesn't matter a whole lot.
> You do not restore tempdb, it is recreated every time the SQL Server is
> restarted.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

[novice Q] sequence in restoring system db

hi,
is there sequence in restoring system db?
shall i start with master, msdb followed by temp or the sequence doesnt
matter?
TIA"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> hi,
> is there sequence in restoring system db?
> shall i start with master, msdb followed by temp or the sequence doesnt
> matter?
> TIA
You will need to restore the master db first. You should check the BOL on
restoring the master database.
Do a search for "Restoring the master Database from a Current Backup"
After that, the other databases order doesn't matter a whole lot.
You do not restore tempdb, it is recreated every time the SQL Server is
restarted.
Rick Sawtell
MCT, MCSD, MCDBA|||got it...thanks rick
"Rick Sawtell" wrote:

> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:1A6DE952-27A0-4C19-B18E-AAF1C69F8A59@.microsoft.com...
> You will need to restore the master db first. You should check the BOL on
> restoring the master database.
> Do a search for "Restoring the master Database from a Current Backup"
> After that, the other databases order doesn't matter a whole lot.
> You do not restore tempdb, it is recreated every time the SQL Server is
> restarted.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Quote:

Originally Posted by daxter

hi
i m connect to the sQL SERVER using system DSN in JREPORT
but it is not working
get the following error
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name

Try using

\Control Panel\Administrative Tools\Data Sources (ODBC)

And System DNS tab up the top of that window

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

odbc_pconnect() [function.odbc-pconnect]: SQL error: [Microsoft][ODBC Microsoft Access Driver] System resource exceeded., SQL state S1001 in SQLConnect

we got the error with access 2000 database and PHP as prog. language .

we created dsn for the connection.

reboot solves the problem. but we need another solution better than this.

You might be running a query that is returning too many records.

Try limiting the query by usng the WHERE clause. Try adding more memory to your computer

Also shifting to SQL Server 2005 for larger databases would improve performance.

Regards,

http://www.Designing-Systems.com

|||You might also want to check out that you do not keep creating new connections instead of reusing existing ones. Check your PSP settings
(if you haven't already) and see whether you have pooling support from PHP or ODBC driver manager.|||

Hi there,

we solved this problem after converting access db to mysql. It solves problem for this.

thanks

|||

If the problem is any of the problems suggested by the above posters, then shifting underlying database representation will just defer the problem until your database gets larger. While your current solution has clearly reduced the pressure to fix the problem, looking into reducing query load, connection usage, and memory overhead on the client side will certainly be beneficial for building a strategy to grow your database.

Hope this helps,

John (MSFT)

|||

We solved this issue. Please close this thread.

Thank you

Jitendra Chavan

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your =computer (for example for development/testing). You can install the =Personal Edition or the Developer Edition of SQL Server to your desktop =machine.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> > my OS is winXP professional edition.
> Anything wrong '
> please help
> >|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
--
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement
> Only client components will be avaiable for installation ]
Also a true statement
> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =SQL Server do not install on to desktop operating systems. If you want =to install SQL Server onto your desktop operating system you will need =to install the Personal Edition, the Developer Edition, or a trial =edition.
> Anything wrong '
You are trying to install SQL Server onto an operating system that it =does not install on.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
> > "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
> > You do have a few options if you need the DBMS installed on your =computer
> (for example for development/testing). You can install the Personal =Edition
> or the Developer Edition of SQL Server to your desktop machine.
> > -- > Keith
> > > "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> > [Microsoft SQL server 2000 standard edition server component is not
> > supported ont this operation system
> > Only client components will be avaiable for installation ]
> >
> > my OS is winXP professional edition.
> > Anything wrong '
> > please help
> >
> >
> >

[help] SQL Error - I/O Error 2 (The system cannot find the file specified)

Windows 2000 Server SP4 + SQL Server 2000 Enterprise Editon SP3,RAID5.

the windows event log give the following error information:

I/O error 2(The system cannot find the file specified) detected during write at offset 0x0000010c6c4000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\GJSZBANK_Data.MDF'.

I have searched microsoft knowledge base and got this article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339

but don't understand some contents in the topic:

For example, if you encounter the following error message in the SQL Server Errorlog file, SQL Server encountered operating system error 2 when it uses a Windows API call to write to the tempdb primary database file:

Error: 823, Severity: 24, State: 4
I/O error 2(The system cannot find the file specified.) detected during write at offset 0x00000000284000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL\data\tempdb.mdf'

Because SQL Server has already successfully opened the file and did not receive an Invalid Handle error, the error is likely being raised in a lower-level kernel software component, such as the file system or a device driver. This problem does not indicate a problem in SQL Server, and it must be investigated as an issue with the file system or a device driver that is associated with the file.

Does that mean this is not a SQL Server error?
Does that mean something wrong with my operating system? or something wrong with my hard disk?Are there any errors in the SQL errorlog? Or is it only in the NT Event log?

[HELP!] How do you make the database path relative in the connection string?

Hi everyone,

I am working on a Hospital Information System project with a team of 6.Each one of us builds or modifies a part of the system and shares the project over a common repository. The problem here is that we use the absolute path of the database in our connection string. Although the directory structure of our project is the same for each member, since the main project folder itself is stored in different locations on each person's computer (for example, one may have it stored in c:\My Documents and the other in d:\ My Documents), we are forced to modify the connection string manually each time someone else from the team updates the repository with the database. How do we make the path of the database relative so that we don't have to modify the connection string manually each time after receiving an update from the repository?

Your help is greatly appreciated.

If you're referencing the path, then I wonder what database you are using. e.g. for MSSQL you would refer to a server and the database on that server, generally just '.' for a local server

Lot's of ways you could do this, e.g. I've just been playing with clickonce install and this is one I use;

connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\dbRaptor_Data.mdf;Integrated Security=True;User Instance=True"

[File System Task] Error: An error occurred with the following error message: "Access to th

Hi -

I have an File System Task that copies a file from one directory ot another. When I hard code the target directory (c:\dir\file.txt) it works fine. When I change it to a virtual directory (\\server\dir\file.txt) I get a security error:

[File System Task] Error: An error occurred with the following error message: "Access to the path '\\grace\hbtest\to\S2TMM_Live_Title_000002.xml' is denied.".

Where do I change the security settings?

Thanks - Grace

Security to network shares is dependent on the user who is running the package. If you are running it yourself, make sure you have permissions to the share. If you are running it from SQL Agent, you might need to use a proxy account (search for SQL Agent Proxy in Books Online) to access it.

[Bug?]Exception thrown in SSCE 3.5 Beta2 but not in 3.5 beta1.

Hi,

I replace the reference assembly System.Data.SqlServerCe with version 3.5 beta2 in Microsoft.Practices.EnterpriseLibrary.Data.SqlCe. When I used the Data.SqlCe block in application, an exception ("Cannot access a disposed object named SqlCeConnection") threw. This didn't occur in SSCE 3.5 beta1 and early versions.

Finally I found the difference between beta1 and beta2.

In the SqlCeConnection class, there is a RemoveWeakReference method. this is code snippet of beta1:

internal void RemoveWeakReference(object value) { if (this.weakReferenceCache != null) { this.weakReferenceCache.Remove(value); } }

and this is for beta2:

internal void RemoveWeakReference(object value) { if (this.weakReferenceCache == null) { throw new ObjectDisposedException("SqlCeConnection"); } this.weakReferenceCache.Remove(value); }

So, if we dispose a connection before a command, such as:

SqlCeConnection cn;SqlCeCommand cmd;... cn.Dispose();cmd.Dispose(); // Error, an exception will be threw. Is it a bug of Beta2?

This is a issue in Beta2. Most probably we will fix in SSCE 3.5 RTM.

The Bug Id: 13211 tracks this issue.

-Vamshi Krishna.

[Bug?]Exception thrown in SSCE 3.5 Beta2 but not in 3.5 beta1.

Hi,

I replace the reference assembly System.Data.SqlServerCe with version 3.5 beta2 in Microsoft.Practices.EnterpriseLibrary.Data.SqlCe. When I used the Data.SqlCe block in application, an exception ("Cannot access a disposed object named SqlCeConnection") threw. This didn't occur in SSCE 3.5 beta1 and early versions.

Finally I found the difference between beta1 and beta2.

In the SqlCeConnection class, there is a RemoveWeakReference method. this is code snippet of beta1:

internal void RemoveWeakReference(object value) { if (this.weakReferenceCache != null) { this.weakReferenceCache.Remove(value); } }

and this is for beta2:

internal void RemoveWeakReference(object value) { if (this.weakReferenceCache == null) { throw new ObjectDisposedException("SqlCeConnection"); } this.weakReferenceCache.Remove(value); }

So, if we dispose a connection before a command, such as:

SqlCeConnection cn;SqlCeCommand cmd;... cn.Dispose();cmd.Dispose(); // Error, an exception will be threw. Is it a bug of Beta2?

This is a issue in Beta2. Most probably we will fix in SSCE 3.5 RTM.

The Bug Id: 13211 tracks this issue.

-Vamshi Krishna.

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
Hanky
Do you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"Çѱ⿵" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[241] Startup error: Unable to initialize error reporting system

When I try to start the SQL Server Agent I am getting this error.
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
Thsi is very frustrating and i cant put up the DB until im sure that I
can have my backups working. Anyone know the solution to this?no one?

@@Identity returns a decimal?

After doing an insert, I am using a System.Data.SqlClient.SqlDataReader to fetch the identity of the inserted row with the following code:

dbCommand.CommandText = "SELECT @.@.IDENTITY As LogID SET NOCOUNT OFF"
Dim dataReader As System.Data.SqlClient.SqlDataReader = dbCommand.ExecuteReader
dataReader.Read
dataReader.GetInt32(0)
dataReader.Close

The problem is that I'm getting an invalid cast exception. If I use dataReader.GetDataTypeName(0), it tells me that value is a decimal? This is odd because the identity column in the SQL table is an int (size: 4). When I use very similar code for another database on the same server, it works.
Anybody have any ideas?

According to the SQL Books Online @.@.Identity is of type numeric (not integer). This would explain why it is returned as decimal instead of an integer.
Brian

|||@.@.Identity doesnt return the ID from the same scope. You should use SCOPE_IDENTITY and furthermore, you should use a stored procedure, which does the insert AND returns the new ID.|||

Hi,
I'm adding a simple stored procedure to show a sample for SonuKapoor's note

CREATE PROCEDURE SiteCreate
(
@.SiteName as nvarchar(100)
)

AS

INSERT INTO Site SELECT @.SiteName, 1

SELECT SCOPE_IDENTITY()

GO

Eralper
http://www.kodyaz.com

|||If we're going down the, "You don't want to do it like that route" then you shouldn't 'SELECT' the value back, you should use an OUTPUT param, and also include the SET NoCount ON, oh oh oh ;) use INSERT ([cols]) VALUES ([values]) syntax, don't select into the insert like that.