Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Thursday, March 29, 2012

database compatibility between sql 2005 standard v/s sql 2005 64 bit

I am a newbie developing a web site. My local machine has sql 2005 standard edition on it. The host that I am trying to use only has sql 2005 64 bit version.

would I be able to do the use the same database between the two ( i.e. once my site is running at host, would I be able to download the database on my local machine, make changes to my site and then upload again on the hose without any glitches?). In addition, how about sql express doing the same with sql 2005 64 bit.

Thanks a lot for taking time to read the post.

get a new host lol...come to my employeer, www.hosting.com. we offer express & std 32BIT lol who only offers 64bit.

Monday, March 19, 2012

Database auto-recovery after server startup

Hi All,
There is a relative-large Database (>12GB in size) in my SQLServer. It
can run as usual without restarting pc machine. After reboot the machine,
the large database would automatically recover for a long time (more than 5
hours). What should the problem be and what can i do for it? Please give
some advice. Thank you !Hi,
As a initial step,
Before rebooting the server please stop the SQL Server service and once it
is sucessful you can restart the Machine.
The only issue I can forsee is " The machine should have been rebooted while
a huge batch process is going on". Due to this after reboot
the Rollback and Roll forward will happen and during this time the database
will be in recovaring status.
Thanks
Hari
MCDBA
"Derek" <dereklim@.southasiagroup.com.hk> wrote in message
news:#wlYpfO1DHA.1272@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> There is a relative-large Database (>12GB in size) in my SQLServer. It
> can run as usual without restarting pc machine. After reboot the machine,
> the large database would automatically recover for a long time (more than
5
> hours). What should the problem be and what can i do for it? Please give
> some advice. Thank you !
>|||Also check the sp_configure recovery interval in minutes,,, it probably
needs to be 0, or < 5.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Derek" <dereklim@.southasiagroup.com.hk> wrote in message
news:%23wlYpfO1DHA.1272@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> There is a relative-large Database (>12GB in size) in my SQLServer. It
> can run as usual without restarting pc machine. After reboot the machine,
> the large database would automatically recover for a long time (more than
5
> hours). What should the problem be and what can i do for it? Please give
> some advice. Thank you !
>

database attaching

we have a pllication that uses MSDE databases, we send out updates we detach
copy new file in and reattach.
Problem: I have a couple of machine the MSDE server want allow the mdb files
to attach. WE remove the current log files after the detatch. Almost like the
machine does't know the SQL server exists anymore.
Hi,
Are you facing the issue to attach the database only with MDF? If yes then
try to attach the database using below command:-
EXEC sp_attach_single_file_db @.dbname = 'DBNAME', @.physname =
'd:\MSSQL\Data\DBNAME.mdf'
Thanks
Hari
SQL Server MVP
"msatullo" <msatullo@.discussions.microsoft.com> wrote in message
news:FA3791F6-F23A-44FE-B6BD-95753C70628C@.microsoft.com...
> we have a pllication that uses MSDE databases, we send out updates we
> detach
> copy new file in and reattach.
> Problem: I have a couple of machine the MSDE server want allow the mdb
> files
> to attach. WE remove the current log files after the detatch. Almost like
> the
> machine does't know the SQL server exists anymore.
|||The databases are attached when the program starts
I get the following errors when the program tries to attach
-2147024769 automation error- the specified proceedure not found
"Hari Prasad" wrote:

> Hi,
> Are you facing the issue to attach the database only with MDF? If yes then
> try to attach the database using below command:-
> EXEC sp_attach_single_file_db @.dbname = 'DBNAME', @.physname =
> 'd:\MSSQL\Data\DBNAME.mdf'
> Thanks
> Hari
> SQL Server MVP
> "msatullo" <msatullo@.discussions.microsoft.com> wrote in message
> news:FA3791F6-F23A-44FE-B6BD-95753C70628C@.microsoft.com...
>
>

Thursday, March 8, 2012

Database access by machines running SQL Servers 2005 32-bit and 64-bit

Hello

We have 1 machine running SQL Server 2005 x64 (64 bit). The other machine is backing this SQL Server up. It is a 32-bit machine, so it requires (?) a 32-bit version of SQL Server 2005.

Would this back-up machine work correctly on a database previously managed by a 64-bit machine and vice versa.

Thank you!

Yes, in terms of connection and administration you won′t feel any difference. But you only can install 32bit software on a 32bit system.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

If my DEV box is 32 bit and my PROD box is 64 bit:

can I deploy (or migrate) from DEV to PROD. The DEV box would have the 32bit SQL Server and the PROD would have the 64 bit SQL server. But if I deploy what I wrote and created there on 32 bit will it run on the 64 bit?

CLR stored procedures?|||No, the things that were developed on the DEv machine can be deployed without any problem on the production machine as from your description. On the Prod system the 64bit framework will take care of the assemblies.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de