Showing posts with label concerning. Show all posts
Showing posts with label concerning. Show all posts

Monday, March 12, 2012

ms sql mdf database file attached vs created on sql server

Hi all

I have a question concerning sql database mdf files. In the old days I would user a ms access database. This file would be stored with the actual web files and would utilise a dsn connection.

I have noted when designing with vwd 2005 express it allows you to use 2 methods of creating a mdf database. You can either create it as an attachment mdf or you can create it directly using sql manager.

My question is, if you create the mdf database as an attachement file can you store it in the same manner as if you where using a ms access database, meaning can you store it with the web site's files so it uses the file storage allocated size and then create a connection similar to a dsn (but for sql) to the isp's sql engine or does it have to be uploaded to the isp' s sql server.

The reason for this question is some of my customers do not want to pay the extra cost to have an sql allocation, however I do not want to go back to using old asp methods to create advanced sites as I prefer using stored procedures.

Any help will be appreciated

Hi,

you can attach your .mdf file (SQL Server Express) to a database (Attaching a .mdf file when you don't have the .ldf file available). However I think the hosting company will charge your customers for attaching it. To my knowledge you don't have a replacement available like DSN.

Grz, Kris.

|||

Hi there,

My first website I did using Visual Studio I used an sql express database. Most hosting companys only use SQL server so you'll have to do some changes to your express database to get it hosted. So it doesnt really matter which way you design your database.

The hosting company will usually place your database on a separate secure server where you'll be able to access through SQL Server Manager once you have a static IP address. I'm not sure which hosting company you use but I live in Ireland and the best company here for windows hosting iswww.blacknight.ie

I use the standard windows hosting which allows you have up to 16 websites and 16 SQL server databases. An excellent company.

I recommend if you are going to use this a lot, upgrade your package to Visual Studio pro and this includes SQL Server Developer edition which allows you to create a SQL Server 2005 database which makes it easier when you go to publish your application.

Hope this is some use to you.

Anthony

|||

Hi Kris

So what you are saying is you can attach a database to an sql server without having to import it directly. Which means the database can run externally from the sql server. My hosting company I think offers it for free if you are attaching and they have a control panel which makes it user friendly to do this by yourself. I will contact them again to verify. www.sahost.co.za

|||

Hi,

about 1,5 years ago I tried out a free hosting for ASP.NET 2.0 where you could upload a .mdf file to and in their admin pages they provided such an attach procedure. Unfortunately I don't remember their name.

Grz, Kris.

Saturday, February 25, 2012

MS SQL 2000 Server 'point in time' restore

Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank You
Robert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>
|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert

MS SQL 2000 Server 'point in time' restore

Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported b
y
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value spe
cified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is te
rminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup devic
e type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE us
ing disk (or possibly tape) and
see whether it work fine...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfigurati
on (60000, &vdiConfig) function ca
ll
> fails with VD_E_TIMEOUT return value and the following message is reported
by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid valu
e specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore.
We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfigurati
on
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert

MS SQL 2000 Server 'point in time' restore

Hello,
We encountered problem concerning MS SQL 2000 point in time restore. Our
backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
VDI. We performed the following combined restore session:
[SCENARIO]
a) Database restore from full backup session, by executing the following
Transact-SQL:
RESTORE DATABASE [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH NORECOVERY;
b) Transaction log restoration which backup was finished on 7/28/2004
2:00:30 PM.
RESTORE LOG [Northwind] FROM
VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
[PROBLEM]
MS SQL backup/restore agent successfully restores full backup version and
leave Nortwind database non-recovered.
When transaction log restore process starts,
IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
fails with VD_E_TIMEOUT return value and the following message is reported by
MS SQL 2000 Server:
<Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
for STOPAT parameter.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
abnormally.
We started several restore sessions and always got the same error when
session was started with 'STOPAT' parameter. But at some point restore
session happened to work and we were unable to reproduce problem anymore. We
have also seen customers facing the same problem.
Sessions started with no 'STOPAT' parameter specified always went OK.
[QUESTIONS]
We would appreciate if you can help us with the following answers:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified?
2. Is there any workaround available?
[ENVIRONMENT]
Environment:
- MS SQL 2000 Server with SP3a installed
- Windows 2000 SP4
- Regional Settings set to English
Thank YouRobert,
Seems you are using a 3:rd party backup product (judging by the backup device type: VIRTUAL_DEVICE =). The
vendor of this is probably where you have to look for support.
To determine whether that is the case, I suggest that you try the RESTORE using disk (or possibly tape) and
see whether it work fine...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"robert.cokan" <robert.cokan@.discussions.microsoft.com> wrote in message
news:E4B763F8-09FD-4241-9FDF-331E7DE07819@.microsoft.com...
> Hello,
> We encountered problem concerning MS SQL 2000 point in time restore. Our
> backup/restore agent integrates to MS SQL 2000 Server through MS SQL 2000
> VDI. We performed the following combined restore session:
> [SCENARIO]
> a) Database restore from full backup session, by executing the following
> Transact-SQL:
> RESTORE DATABASE [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH NORECOVERY;
>
> b) Transaction log restoration which backup was finished on 7/28/2004
> 2:00:30 PM.
> RESTORE LOG [Northwind] FROM
> VIRTUAL_DEVICE = 'Data Protector_(DEFAULT)_Northwind_11_20_49'
> WITH STOPAT = '7/28/2004 2:00:20 PM', RECOVERY;
>
> [PROBLEM]
> MS SQL backup/restore agent successfully restores full backup version and
> leave Nortwind database non-recovered.
> When transaction log restore process starts,
> IClientVirtualDeviceSet2::GetConfiguration (60000, &vdiConfig) function call
> fails with VD_E_TIMEOUT return value and the following message is reported by
> MS SQL 2000 Server:
> <Microsoft SQL-DMO (ODBC SQLState: 42000):c91>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid value specified
> for STOPAT parameter.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating
> abnormally.
>
> We started several restore sessions and always got the same error when
> session was started with 'STOPAT' parameter. But at some point restore
> session happened to work and we were unable to reproduce problem anymore. We
> have also seen customers facing the same problem.
> Sessions started with no 'STOPAT' parameter specified always went OK.
>
> [QUESTIONS]
> We would appreciate if you can help us with the following answers:
> 1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
> failure when 'STOPAT' parameter is specified?
> 2. Is there any workaround available?
>
> [ENVIRONMENT]
> Environment:
> - MS SQL 2000 Server with SP3a installed
> - Windows 2000 SP4
> - Regional Settings set to English
> Thank You
>|||Hello Tibor,
thank you for your help. However, we need to say that we are backup vendor.
We have addressed this question to MS Support due to we were unable to find
explanation for 'Invalid value specified for STOPAT parameter' message
reported by MS SQL Server. Please help us by providing answers to the
following questions:
1. what can be a reason for IClientVirtualDeviceSet2::GetConfiguration
failure when 'STOPAT' parameter is specified? Please also note that restore
session does not always fail (see [PROBLEM] section below).
2. Is there any workaround available?
3. Under What circumstances MS SQL 2000 Server reports 'Invalid value
specified for STOPAT parameter' message?
Thank you,
Robert

Monday, February 20, 2012

MS SQL - Professional Assistance required concerning Capacity.

Hi there,

We are currently developing a E-Com research site where subscribed members can conduct market research. The web site is developed and ready to go, however we are undecided what is required on the Database side and could do with some of your expert help.

Users will be conducting research on our MS SQL database. The database holds every product sale made by a select number of consumer good companies. The database holds 12 million records at any one time, however overall the database is very static and is not updated online. We intend to only store 1 months data, therefore on a weekly basis we delete old & add new records.

We are offering three categories of searches on the DB.
1. By Seller
2. By Category (i.e. Hair Care, Laundry etc)
3. By Sale.

The first two searches are not performance intensive as they are compiled and stored in the database - therefore no need for calculation online. Our main concern is the 3rd report. This report is where we allow the user to search for a specified search string. Therefore in the main table that holds all the sales, we have a full-text index for the field "Product Description".

What we are unclear on is the Capacity requirements regarding providing such functionality. I.e What server do we require?

We have researched many articles and have absorbed all the information regarding multiple disk controllers, lots of memory etc.. etc.. However we still have not been able to obtain an idea on what Server would serve our purposes. For example: would the following server do the job?

2 x 2.4Ghz Hyper-threading Xeon CPUs with 512Kb Cache and 400MHz System Bus
2GB Samsung RAMBUS 800-45 Memory (RIMMS / RDRAM)

A lot is determined by the usage, i.e. how many queries are executed per minute etc. At present we do not have a clear idea on the number of users. However we are not truely concerned about this as the 3rd report needs to execute and return within a short period of time. That is our main concern.

Therefore our question is as follows: If you were going to host a database that consisted of 12 million records & full-text indexing which had to be queried in a few seconds, what would you purchase?

We ask you to consider that funds are extremely tight and although the new latest server may do the job, it is most likely out of our budget. We are looking for the most cost effective solution but still statisfying the purpose.

Kind regards
AngusPerformance tuning isn't an exact science. Especially when there isn't a good test base where you can make and test your proposed changes, the whole thing is subject to a lot of opinion rather than fact.

In my opinion, your search will almost certainly be disk bound rather than CPU bound. Fast disk is important, but redundancy gets expensive fast... I'd suggest all of the RAM you can and the fastest drive subsystem that you can afford.

-PatP